[API-M-4.0.0] Missing some instructions to configure ForgeRock as a key manager
Open
Nobody has claimed this yet.
API-M-4.0.0
Docs/TW
Priority/High
Severity/Major
Type/Bug
- Dominant language
- CSS
- Stars
- 99
- Forks
- 708
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 22
Description
Description:
The documentation lacks following important instructions to configure ForgeRock as a key manager.
- Steps or reference for installing ForgeRock.
- In step 1.1.4, the value for
Scope Implementation Classshould beorg.forgerock.openam.oauth2.OpenAMScopeValidator. - In step 1.1.4 the screenshot is missing.
- In step 1.1.5 Service Provider should be changed as Services.
- In step 1.2.1
Realm -> OAuth 2.0 -> Applicationsshould be changed asRealm -> Applications -> OAuth 2.0. - In step 1.2.1 both
am-introspect-all-tokensdynamic_client_registrationshould be added to Default Scope(s) as well. - In step 1.2.2
Applications -> Client ID of the Appshould be changed asApplications -> OAuth 2.0 -> Client ID of the App.
Suggested Labels:
API-M-4.0.0
Affected Product Version:
API-M-4.0.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the ForgeRock key-manager documentation covering steps 1.1.4 through 1.2.2 and review the existing instructions and screenshots. Update the seven listed installation, navigation, field-value, scope, service-name, and screenshot items; it is done when the configuration guide includes all requested corrections and references.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100