OpenLiberty / OpenLiberty/docs

Info from Authorization topic in KC

Open
#1,879 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
14
Forks
58
Avg merge
4m
Merged PRs (30d)
35

Description

This is a working issue for now - don't assign out yet.

https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/cwlp_authorization.html#d337475e272

There are chunks of info in this topic that don't really follow from one another but also we don't document anywhere in OL docs yet. We're looking into whether any/all of this info should be added to OL docs and what the context of each is so that it's added to the right place. The main chunks that we're looking at are Special subjects; Access IDs and authorization; OAuth; Authorization for applications when role mapping binding is not provided. However, if there's anything else in there that should be pulled out, we should note that.

Ultimately, we need to record in the KC spreadsheet which bits we do and which we do not need to transfer to OL docs (and why we came to that decision) so that we have a record for the future and they don't accidentally get moved across "just in case".

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked IBM Knowledge Center authorization topic and review the sections on Special subjects, Access IDs and authorization, OAuth, and authorization when role mapping binding is not provided. Determine the context and whether each section belongs in Open Liberty docs, noting the decisions and reasons in the KC spreadsheet. Also record any additional relevant content found during the review.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.