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

Discover: set up principals (traits) fails when user is imported from Okta #47901

Closed
marcoandredinis opened this issue Oct 24, 2024 · 0 comments · Fixed by #47944
Closed

Discover: set up principals (traits) fails when user is imported from Okta #47901

marcoandredinis opened this issue Oct 24, 2024 · 0 comments · Fixed by #47944
Labels
bug discover Issues related to Teleport Discover okta-service

Comments

@marcoandredinis
Copy link
Contributor

marcoandredinis commented Oct 24, 2024

When enrolling a new resource using the Discover wizard, one of the last steps is the Set Up Access.
This step asks the user to configure principals (os logins for SSH Access and db_user/name for Database Access). Those principals are added to the user's traits, which can then be used to access the protected resource.

When the user comes from an SSO, it doesn't have traits and so the step only tells the user how can they achieve the same goal (accessing the resource with a given principal) but using the SSO provider.

However, when the user comes from the Okta integration, we still try to update the user, and that fails with:

Image

Expected behavior:
Explain what the user needs to do to add a given principal to their allowed principals.

Current behavior:
Error Must be Okta service to set "okta" origin is shown.

Bug details:

  • Teleport version: 16.4.6
  • Recreation steps
  • Debug logs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug discover Issues related to Teleport Discover okta-service
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant