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.

Sign up for GitHub

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

Jump to bottom

Is there the need to change the default value of subject_types from uname to public? #151

Open
daisukenishino2 opened this issue May 23, 2021 · 2 comments
Open

Is there the need to change the default value of subject_types from uname to public? #151

daisukenishino2 opened this issue May 23, 2021 · 2 comments
Labels
enhancement New feature or request
Milestone
Release of 02-10 ...

Comments

@daisukenishino2
Copy link
Member

daisukenishino2 commented May 23, 2021 •
edited
Loading

Requirement

As the title says.
@daisukenishino2 daisukenishino2 added the enhancement New feature or request label May 23, 2021
@daisukenishino2
Copy link
Member Author

Answer

Default behavior of this product for external login.
However, when federating, it is preferable to obtain a separate user ID or change subject_types to public.

@daisukenishino2 daisukenishino2 added question Further information is requested wontfix This will not be worked on and removed enhancement New feature or request labels May 23, 2021
@daisukenishino2
Copy link
Member Author

daisukenishino2 commented May 24, 2021 •
edited
Loading

Modifications

Change subject_types to public.

  • "public" or "pairwise" or "uname"
  • uname is a proprietary specification and default value.
  • In public, it returns the user_id as the sub-value.

Support username in scope.

uname

@daisukenishino2 daisukenishino2 added enhancement New feature or request and removed question Further information is requested wontfix This will not be worked on labels Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
Release of 02-10 version
Development

No branches or pull requests
1 participant
@daisukenishino2