Include groups claim steps to Okta SSO page

[akshay196]

Based on this Paralus new feature: https://github.com/paralus/paralus/pull/172

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
website	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 2, 2023 8:38am

[akshay196]

Spell checking is weirdly running on subset of letters from the word. @techmaharaj Do you know how to fix it?

[akshay196]

Showing many spell check errors now. :( Typos CI is not able to parse files correctly, it is purposefully built for source code. @techmaharaj Do you know any alternative CI app for typos?

[niravparikh05]

@akshay196 let's include some more details like how to create a group, add people to groups and also a note that the group name should be the same as the one created in paralus having appropriate permissions

[akshay196]

let's include some more details like how to create a group, add people to groups

Adding people to groups is not a scope of this page/Paralus documentation. Added a reference to Okta user/group management document. Hope it helps.

and also a note that the group name should be the same as the one created in paralus having appropriate permissions

Good point. Added a note at the end.

[techmaharaj]

@akshay196 I think it's important to mention why are we creating a claim here. Currently if you see the documentation, it just starts with 'Creating a Okta SSO Application` and then we talk about adding claims. There has to be a header somewhere that talks about what are claims and why we are adding one.

Also, I don't see where have we mentioned that Okta group name must be similar to Paralus.

[akshay196]

@akshay196 I think it's important to mention why are we creating a claim here. Currently if you see the documentation, it just starts with 'Creating a Okta SSO Application` and then we talk about adding claims. There has to be a header somewhere that talks about what are claims and why we are adding one.

ah, let me add more details.

Also, I don't see where have we mentioned that Okta group name must be similar to Paralus.

Added a note at the end that goes as Okta groups of the user are mapped to Paralus groups based on their names. The groups mapping provides necessary permissions to access Paralus resources after successful login. If a user is not part of any Okta group then admin needs to explicitly configure group for the user in Paralus.. Is it not clear? any suggestions?

[techmaharaj]

Added a note at the end that goes as Okta groups of the user are mapped to Paralus groups based on their names. The groups mapping provides necessary permissions to access Paralus resources after successful login. If a user is not part of any Okta group then admin needs to explicitly configure group for the user in Paralus.. Is it not clear? any suggestions?

Just saw it now, my bad.

I think instead of this being at the end of the document, it will make more sense to put it where you're adding the claim.

So that's where you can mention two things:

• Why are we adding a claim, what it does and why it's required for Paralus
• This note that the group name should be the same as Paralus (the user needs to create a group in Paralus first) and why.

[akshay196]

@techmaharaj @niravparikh05 Made all the changes. Please take a look.

[akshay196]

@techmaharaj Updated PR. Please take a look.

[akshay196]

The spell checker workflow is reporting many false positives. Maintaining ignore list is an extra burden. I have removed the spell check in this PR. Hope this is fine.

[akshay196]

@techmaharaj Thanks for reviewing @niravparikh05 Thanks for merging.