Programmatically using CreateStreamingURL and persistent storage

0

I'm investigating a similar approach to this question on using a custom IdP / authentication process. One thing that isn't clear from the docs is whether the CreateStreamingURL flag for the UserID also propagates through to the persistent storage via S3.

The workflow that I would like is:

  1. User logs into my application, and permissions are checked. All authn/authz logic contained here.
  2. Application uses an AWS service account to call CreateStreamingURL, with e.g. UserID=user1@example.com and UserID=user2@example.com .
  3. Application gives user1 -> url1 and user2 -> url2, such that these sessions are isolated.
  4. Next day, user1 logs in again and gets url1_new, and should be able to see whatever settings / persistence as per the previous session.

Is my understanding of the UserID parameter correct?

1 Answer
0
Accepted Answer

Yes. If the username is the same, the user will get the same home folder and application settings persistence.

profile picture
answered 22 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions