Skip to content
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

Blank Page when accessing Eligibility policy #140

Closed
niven01 opened this issue Jan 10, 2024 · 2 comments
Closed

Blank Page when accessing Eligibility policy #140

niven01 opened this issue Jan 10, 2024 · 2 comments

Comments

@niven01
Copy link

niven01 commented Jan 10, 2024

Describe the bug
This was already reported here #101

After going through the deployment process in here https://aws-samples.github.io/iam-identity-center-team/docs/deployment/deployment_process.html I wanted to add eligibility policies. When i go to the page i got blank

To Reproduce
Steps to reproduce the behaviour:

  1. Log into the application as TEAM admin.
  2. In the left-hand menu go to Administration → Eligibility policy.
  3. Click on Create eligibility policy
  4. Results in blank page in chrome and edge

Expected behaviour
Page allowing me to create Eligibility policy

Desktop (please complete the following information):

  • OS: Windows 11
  • Browser Chrome, Edge
  • Version 1.1.0

Additional context
I've seen the comment regarding Assigning a Permission set to the management account back in Oct 2023. I attempted this but still see a blank page.

It's possible I've done this wrong

I logged into Org Management account
Opened IAM Identity Center
Created a Permission Set with AdminstratorAccess

Is there a fix in the pipeline? Can someone explain the work around using permission sets

@tawoyinfa
Copy link
Contributor

@niven01 usually this is because there is no permission set assigned to the management account. Can you try assigning a permission set to the management account and try again ?

@niven01
Copy link
Author

niven01 commented Jan 10, 2024

Thanks I've literally just done. I had set the permissions set in the wrong account. Effectively had to do this on the master payer account and not what I deemed the managment account

I can confirm I have a work around

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants