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

docs: migrate and write SCIM documentation for Janssen Server #2681

Closed
1 of 8 tasks
ossdhaval opened this issue Oct 20, 2022 · 1 comment
Closed
1 of 8 tasks

docs: migrate and write SCIM documentation for Janssen Server #2681

ossdhaval opened this issue Oct 20, 2022 · 1 comment
Assignees
@ossdhaval
Labels
area-documentation Documentation needs to change as part of issue or PR effort-5 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality priority-4 Minor issue or PR is not relevant to core functions, or relates to the usability of system triaged Issue or PR is fully triaged
Milestone
1.0.14

Comments

@ossdhaval
Copy link
Contributor

ossdhaval commented Oct 20, 2022 •
edited
Loading

Janssen Server needs documentation for SCIM administration. Much content will come from Gluu documentation with adaptation to Janssen where required.

  • Update README with overview #2692
  • Update SCIM module configuration document
  • Update SCIM module logging details document
  • Update SCIM module monitoring instructions document
  • Instructions on how to protect SCIM with OAuth
  • Update SCIM module security consideration
  • Instructions for bulk adding of users
  • Instructions for adding custom attributes
@ossdhaval ossdhaval added kind-enhancement Issue or PR is an enhancement to an existing functionality area-documentation Documentation needs to change as part of issue or PR effort-5 Relative effort required for completion of issue or PR priority-4 Minor issue or PR is not relevant to core functions, or relates to the usability of system triaged Issue or PR is fully triaged labels Oct 20, 2022
@ossdhaval ossdhaval self-assigned this Oct 20, 2022
@moabu moabu added this to the 1.0.4 milestone Nov 3, 2022
@moabu moabu modified the milestones: 1.0.4, 1.0.5 Nov 14, 2022
@moabu moabu modified the milestones: 1.0.5, 1.0.6 Dec 1, 2022
@moabu moabu modified the milestones: 1.0.6, 1.0.7 Jan 9, 2023
@moabu moabu modified the milestones: 1.0.7, 1.0.8, 1.0.9 Mar 1, 2023
@moabu moabu modified the milestones: 1.0.9, 1.0.10 Mar 9, 2023
@moabu moabu modified the milestones: 1.0.10, 1.0.11 Mar 16, 2023
@moabu moabu modified the milestones: 1.0.11, 1.0.12 Apr 5, 2023
@moabu moabu modified the milestones: 1.0.12, 1.0.13 Apr 18, 2023
@moabu moabu modified the milestones: 1.0.13, 1.0.14 May 10, 2023
@ossdhaval
Copy link
Contributor Author

Closing this issue as individual issues are being tracked by their respective GH issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ossdhaval ossdhaval

Labels
area-documentation Documentation needs to change as part of issue or PR effort-5 Relative effort required for completion of issue or PR kind-enhancement Issue or PR is an enhancement to an existing functionality priority-4 Minor issue or PR is not relevant to core functions, or relates to the usability of system triaged Issue or PR is fully triaged
Projects
None yet
Milestone
1.0.14
Development

No branches or pull requests
2 participants
@ossdhaval @moabu