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 Issue] "Set up Wso2 Identity Server as a federated Authenticator" lacks context/ links to certain steps #9064

Open
HussainLatiff opened this issue Feb 27, 2025 · 0 comments

Comments

@HussainLatiff
Copy link

HussainLatiff commented Feb 27, 2025

The steps in this process that lack the ease of use that the rest of the docs have. Especially with providing links to certain actions.

A few key improvements especially for new users to have a better experience could be :

  1. Similar to how there is a link provided for GitHub releases provide an image or link to creating a port offset
    Image

  2. Including the click update after every step so that they make sure they do it and not lose the configs. Include this at the end of step 6 and 7.
    Image

  3. At step 7 maybe include a circle around "+ New Role" and also this UI so the users are not having to guess on their own if the assumptions are correct.
    Image

  4. Similarly at step 8 it could be more descriptive by including the + New user -> Single User and we provide this UI with example values
    Image

  5. This step is too vague, also includes a typo witht he word "assinging" instead word it like this: Select a role -> Go to the Users tab and assigning users to the role. amd include a screen shot.

Image

  1. Small typo that can be addressed, change it to step 15. not 1. and make it devportal not developer role

Image

  1. Step 2 under "Set Up WSO2 API Manager", there is 0 context with this screen shot, needs to atleast include a url or something showing it is the carbon console.

Image

  1. A pain point following the steps 7 to 12 is that this process takes a while and the user gets logged out and loses all that progress when configuring a identity server We need to include a note or something to the extent of, It is best practice to make a few changes to the configurations -> Click finish -> Then edit the Identity server configs, so that the user does not get timed out due to inactivity. (This was the process I used after loosing progress twice)

  2. Finally the ending needs to include how the user can go ahead and use these changes. maybe something like open publisher protal, https://localhost:9443/admin -> Log in via admin portal user configured

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant