-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Authentication issue #959
Comments
I have been trying to find a way to make that work for a while. All of my research shows that it is currently not possible. I embed the iframe in an internal app and we're forced to log in twice, once for our internal app and once for connect. |
What type of connect instance are you using? Amazon Connect supports two types of auth management. In the console, they're labeled as "Connect Managed" and "SAML 2.0". For Connect Managed, you will have to enter a username and password to log in to the account, but for SAML 2.0, if you are already logged into your SSO and your SSO is setup to SAML into the Amazon Connect instance, users shouldn't be required to re-enter the password again. However, in both scenarios, when using Streams to embed CCP, we still have the popup screen to prompt for login. |
A great and often mentioned feature would to be able to send attributes of username/password when initializing the streams api. This feature would probably be implemented by all of the developers using the streams-api inside of an application that was already logged in to. |
Is there any way to authenticate the user without the popup screen by passing username and password directly to some where. also without amazon cognito user pool
The text was updated successfully, but these errors were encountered: