Cannot connect to quicksight when the user is not in the default namespace

Q&A
, ,
1

Hello,

I did create a new Entrprise edition Quicksight account where i did set the authentication method to “Password based or Signle-Sign On”.

With the quicsight API CLI, i did create diffrent namespaces as well as diffrent users in those namespaces.

My issue is that only users that are created in the default namespace could access Quicksight with this url : https://eu-west-3.quicksight.aws.amazon.com/sn

But other users in namespace X for example couldn’t access. They get this error message :

The calculation is not done.

We have not been able to verify your login credentials. Please try again.

Thanks in advance!

2

Hi @ilyasse

Quick URL you are using defaults to the default namespace and may not work directly for users in non-default namespaces. Users in non-default namespaces must be created and authenticated using federated Single Sign-On (SSO) configured with your identity provider (IdP) via IAM federation.

Please refer to the following documentations this might be helpful for you.

3

Hi

if i understand verry well, it is impossible to have users in diffrent namespace authenticate to quicksight directly with url, an SSO configuration is mandatory for them right?

I wonder if it is the only way for them to access quicksight except iam identity center or active directory?

Thank you

4

Hi @ilyasse

Yes, users in non-default (custom) namespaces cannot authenticate directly via the standard URL using password based login, federated Single Sign On (SSO) via IAM is mandatory for them. Custom namespaces support only IAM federated SSO users.

1 Like
5

Hi @Xclipse,

I’d like to add one more question please,

I already have an external IDP that uses OIDC standard. i can use it in order to configure my quicksight users with diffrent namespaces right ?

Is there any configuration needed to achieve that ? Any documentation regarding this ?

Thanks !

6

Hi @ilyasse

Yes, external OIDC IdP can be used to federate Quick users into different custom namespaces, as supports custom OIDC providers through IAM identity federation.

Please refer to the following documentations and videos this might be helpful for you.

1 Like