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

docs(OIDC feature): create documentation for user claims #4851

Closed
ossdhaval opened this issue May 8, 2023 · 3 comments · Fixed by #5882
Closed

docs(OIDC feature): create documentation for user claims #4851

ossdhaval opened this issue May 8, 2023 · 3 comments · Fixed by #5882
Assignees
Labels
area-documentation Documentation needs to change as part of issue or PR
Milestone

Comments

@ossdhaval
Copy link
Contributor

General Guidelines

  • Start by covering the general definition of the feature in a few lines and then point to the appropriate section of the SPEC. Please refrain from repeating what is there in the SPEC already.
  • Try to make the content Janssen Server specific ( e.g. what are the related Janssen Server properties or feature flags, how to change relevant settings using TUI/command line (use the screenshots), recommendations around recommended values, use-cases)
  • Follow the documentation contribution guidelines.
  • Feel free to refer to content available in Gluu documentation (or any other IDP) if the content doesn't need to be customized for Janssen Server

Document Location

https://docs.jans.io/head/admin/auth-server/openid-features/user-claims/

Suggested sections

  • Built-in claims
  • Adding custom claims
  • Claim uniqueness and validation
@ossdhaval ossdhaval added the area-documentation Documentation needs to change as part of issue or PR label May 8, 2023
@ossdhaval
Copy link
Contributor Author

@nynymike I suggest consolidating the user claims section with sub-documents becoming sub-sections in one document. Please share your views.

@moabu moabu added this to the 1.0.14 milestone May 10, 2023
@ossdhaval ossdhaval self-assigned this May 15, 2023
@ossdhaval ossdhaval removed this from the 1.0.14 milestone May 22, 2023
@moabu moabu added this to the 1.0.14 milestone Jun 5, 2023
@moabu moabu modified the milestones: 1.0.14, 1.0.15 Jun 20, 2023
@moabu moabu modified the milestones: 1.0.15, 1.0.16 Jul 12, 2023
@moabu moabu modified the milestones: 1.0.16, 1.0.17 Aug 2, 2023
@ossdhaval ossdhaval modified the milestones: 1.0.17, 1.0.19 Aug 10, 2023
@nynymike
Copy link
Contributor

Related : #4556
Perhaps the same person should do both.

@ossdhaval
Copy link
Contributor Author

Hi @duttarnab Assigning this to you as you are working on #4556. As per Mike's comment above.

@ossdhaval ossdhaval assigned duttarnab and unassigned ossdhaval Aug 14, 2023
duttarnab added a commit that referenced this issue Aug 15, 2023
duttarnab added a commit that referenced this issue Aug 15, 2023
duttarnab added a commit that referenced this issue Aug 17, 2023
Signed-off-by: Arnab Dutta <arnab.bdutta@gmail.com>
duttarnab added a commit that referenced this issue Aug 18, 2023
Signed-off-by: Arnab Dutta <arnab.bdutta@gmail.com>
ossdhaval pushed a commit that referenced this issue Aug 22, 2023
Signed-off-by: Arnab Dutta <arnab.bdutta@gmail.com>
devrimyatar pushed a commit that referenced this issue Dec 30, 2023
Signed-off-by: Arnab Dutta <arnab.bdutta@gmail.com>
Signed-off-by: Mustafa Baser <mbaser@mail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment