Tagged: Antigua and Barbuda, Australia, Bahamas, Barbados, Belize, Canada* Dominica, Denmark, Finland, Grenada, Guyana, India, Ireland, Jamaica, Netherlands, New Zealand, Nigeria, Norway, Pakistan, powerful voodoo spells caster in United States of America, St Kitts and Nevis, St Lucia, St Vincent and the Grenadines, Sweden, The Philippines, Trinidad and Tobago., United Kingdom
September 25, 2014 at 10:21 pm #176
We would love to hear what you think about our documentation. It’s an easy way to get involved in the community!
Read our docs. If you find a typo, let us know in a post on this board. If you find a technical error, register for a community account at https://backstage.forgerock.com/#!/account/register . It’s free!
With a community account, you can file a bug report at bugster.forgerock.org. Do it and watch your name rise on the leaderboard.
October 9, 2014 at 3:11 pm #455LudoModerator
- This topic was modified 7 years, 8 months ago by Marius @ForgeRock.
Does the forum support sticky posts ?October 9, 2014 at 3:57 pm #458Marius @ForgeRockSpectatorNovember 3, 2014 at 11:37 pm #1009Aron KozakSpectator
As we have a separate forum for discussions, we should consider deleting this threadNovember 3, 2014 at 11:44 pm #1010
I’ll forward you a related request that I’ve made to Marius.
MikeJune 21, 2018 at 9:16 pm #22362voxtelParticipant
I found countless errors and information that was either incorrect or obsolete, but writing down all of this here would take forever.
Most of the people finding errors are on the documentation page, not the forum page. I would suggest you add a system to flag mistakes inside the documentation page, so we could flag errors immediately as we see them, without needing any more complications. If people can instantly flag mistakes without having to come here for every single error, I believe you would get much more feedback.
We have such a system — but perhaps we haven’t publicized it well enough. For example, if you have comments on the IDM Installation Guide for IDM version 6, you’d navigate to: https://backstage.forgerock.com/docs/idm/6/install-guide/
Look for the “bug” icon in the upper right corner: .
Select the icon. You’ll see a screen where you can provide feedback:
When others use this feature, we on the ForgeRock documentation team see this feedback via email, and we try to respond with at least an action plan (typically a JIRA) fairly quickly.
I encourage you to try it! I hope you’ll be pleased with the results.
June 21, 2018 at 10:37 pm #22367voxtelParticipant
- This reply was modified 4 years ago by Mike Jang.
Thanks a lot, I hadn’t seen that and will be sure to use it! Obviously the ability to select where the problem is would make things easier for you, but that’s already a good start and I’ll be sure to flag all errors from now on!
have a nice day :)June 21, 2018 at 10:45 pm #22368
We look forward to your feedback, and I dare say we’re eager to hear about any and all problems with our documentation. FWIW, we’re exploring options such as Diigo and Juntoo.
MikeSeptember 6, 2018 at 6:37 pm #23135amthomsonParticipant
The first issue I had was trying to understand the difference between products like AM vs. OpenAM as well as which versions of each product worked together. I currently have OpenDJ, OpenAM and OpenIDM and have found it very difficult to follow the documentation to understand the best practices of using these products from a RESTful standpoint.September 6, 2018 at 8:42 pm #23137
Essentially, you’ve asked several questions. (I’m not sure if I’m answering the right questions, so let us know.)
1) “difference between products like AM vs. OpenAM”.
AM is short for “Access Management”, which is the current version of our product.
For compatibility with our other products, we changed the numbering sequence last year. So you’ll see (in reverse order, newest on top):
2) As for products that work together, you’ll have to refer to the release notes for each product. If the release notes don’t clarify, let us know!
2a) I’ve set up blog posts detailing how AM, IDM, and DS work together, e.g. https://forum.forgerock.com/2018/05/forgerock-identity-platform-version-6-integrating-idm-ds/
3) Re: Best practices using our products from a RESTful standpoint: we have extensive official documentation for REST for each of our products. Mark Craig has recently posted a series of blog posts summarizing how to set up REST for each of our products, ref https://marginnotes2.wordpress.com/2018/08/28/using-the-forgerock-am-api-explorer/
MikeJanuary 4, 2019 at 2:01 pm #24361hbolchatParticipant
issue on SSL configuration on openDJ
un.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
February 6, 2020 at 9:50 pm #27568William HeplerParticipant
- This reply was modified 3 years, 5 months ago by hbolchat.
Can you provide more context, If you have doc feedback like a typo you can click the feedback bug while in the doc’s to give that feedback directly to our teams.
March 17, 2021 at 9:04 pm #28485usernameabcdParticipant
- This reply was modified 2 years, 4 months ago by William Hepler.
<img src=x>March 17, 2021 at 9:08 pm #28488
You must be logged in to reply to this topic.