- Newest
- Most votes
- Most comments
The URL format you're using is not correct for automatically starting an application in AppStream 2.0. When using AppStream 2.0 with User Pool authentication, you don't directly construct the URL for launching applications. Instead, the process works differently.
For User Pool authentication, AppStream 2.0 sends an email to users when they are created or assigned to a stack. This email contains a URL that the users should use to access their applications. When users click on this URL, enter their credentials, and choose "Connect", they are directed to the AppStream 2.0 interface.
To automatically launch an application when a user logs in, you need to configure this behavior in your AppStream 2.0 stack settings, not through a URL. Unfortunately, the provided information doesn't specify how to set up automatic application launch for User Pool authentication.
If you need more control over the application launch process, you might want to consider using the programmatic authentication method instead of User Pool. With programmatic authentication, you can use the CreateStreamingURL API operation to generate a temporary URL for starting an AppStream 2.0 streaming session. This method allows you to pass session context information, which could potentially be used to specify an application to launch automatically.
However, it's important to note that switching to programmatic authentication would require significant changes to your authentication flow and would involve writing code to make API calls to AWS.
If you want to stick with User Pool authentication, I recommend reaching out to AWS support for specific guidance on how to configure automatic application launch for your use case, as the available information doesn't provide a clear solution for this scenario with User Pool authentication.
Sources
AppStream 2.0 User Pool - Amazon AppStream 2.0
CreateStreamingURL - Amazon AppStream 2.0
Authentication - Best Practices for Deploying Amazon AppStream 2.0
answered 2 years ago
Relevant content
asked 3 years ago
asked 2 years ago
asked 6 years ago
