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

Invite team in the environment is not listing all the groups that I am part of in AD Idp #417

Closed
mvidhu opened this issue Apr 18, 2023 · 4 comments

Comments

@mvidhu
Copy link

mvidhu commented Apr 18, 2023

Describe the bug

I am trying to invite other team (AD group) to my environment in Data.All, however I cannot see the groups that I am part of since they are not in Cognito groups.
Since our organization is using Azure AD for authentication, we expect to see the AD groups also as part of the environment invite functionality.

How to Reproduce

*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*

Integrate data.all with AD using Azure AD integration steps.
If you are part of multiple groups, you can see the custom.saml.groups in cognito showing list of groups.
Navigate to Data.All environments and try to invite a team you are part of. Dropdown only shows cognito group and does not integrate with AD teams.

Expected behavior

We should be able to invite a different team from AD groups.

Your project

No response

Screenshots

No response

OS

Mac

Python version

3.11

AWS data.all version

0.5.0

Additional context

No response

@dlpzx dlpzx added type: newfeature New feature request status: not-picked-yet At the moment we have not picked this item. Anyone can pick it up priority: low labels Apr 20, 2023
@anmolsgandhi anmolsgandhi added the future-decision not prioritized but could evaluate in future label Sep 6, 2023
@anmolsgandhi anmolsgandhi removed the future-decision not prioritized but could evaluate in future label May 23, 2024
@anmolsgandhi
Copy link
Contributor

@noah-paige i believe we now support other IDPs as of 2.x version? can we close this?

@noah-paige
Copy link
Contributor

Yes this should be resolved and list groups should appear appropriately as of v2.2 with the PR - #897

This requires the data.all admin team to configure data.all to work with a custom IdP (non-Cognito) - there are detailed instructions for how one can configure data.all in this way in data.all's Documentation Pages Deploy to AWS Steps- Section 6.1 (Important) - Configure data.all to use external Idp

@noah-paige
Copy link
Contributor

I will close this issue by EOD today since it is implemented in the latest data.all - please let me know if any other questions or concerns and thanks for opening up this issue!

@anmolsgandhi anmolsgandhi added status: closing-soon and removed type: newfeature New feature request priority: low status: not-picked-yet At the moment we have not picked this item. Anyone can pick it up labels Jul 17, 2024
@dlpzx dlpzx closed this as completed Sep 5, 2024
@dlpzx
Copy link
Contributor

dlpzx commented Sep 5, 2024

Closed due to inactivity. If any support is needed do not hesitate to open a new issue.

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

No branches or pull requests

4 participants