docs: updated faq due to keycloak process change #180
Conversation
- adjusted process for the user creation (technical/business) due to changes in keycloak prozess - adjusted/refurbished several descriptions.
- adjusted structure - adjusted markdown
- adjusted structure - adjusted markdown
Co-authored-by: Phil Schneider <[email protected]>
There was a problem hiding this comment.
Great that you looked into updating those FAQs, I just noticed that they are really outdated
- I think the company role question should be moved to the portal documentation as it doesn't have any connection to iam
- the portal role question should maybe be rewritten to be applicable to every shared service not just portal and the portal seeding/db updates should be moved into the portal docs
- for
What is the difference between roles & permission: there should maybe be mentioned that the Keycloak terminology for what we call here roles iscomposite rolesand the Keycloak terminology for what we call often permissions or details roles is justroles... - I don't think this match between uuid in Keycloak and in portal is needed (at least not anymore):
1st to get the role id move into your browser open the user role configuration and copy the second UUID from the url.For adding the role into the portal seeding data some autogenerated uuid can be used
|  | ||
|
|
||
| 2. Create the same role inside the portal db (either via a delta migration job) or via sql. | ||
| #### 2. Create the business role inside the portal db (either via a delta migration job) or via sql |
There was a problem hiding this comment.
Might be better to remove the way via sql entirely as that makes it seem as we somehow suggest that but from a good practice point of view, we should only propagate the way via updating the portal seeding data, which here is called delta migration job as that the only sustainable way, via sql might be useful for a short test but nothing else
|
|
||
|  | ||
| #### 2. Create the technical role inside the portal db (either via a delta migration job) or via sql |
There was a problem hiding this comment.
Might be better to remove the way via sql entirely as that makes it seem as we somehow suggest that but from a good practice point of view, we should only propagate the way via updating the portal seeding data, which here is called delta migration job as that the only sustainable way, via sql might be useful for a short test but nothing else
removed spelling errors Co-authored-by: Evelyn Gurschler <[email protected]>
|
Description
Due to keycloak upgrade processes needed an adjustment.
Issue
not needed
Checklist
Please delete options that are not relevant.