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

ENDOC-640 Entando Entando Identity Management System Documentation #658

Merged
merged 2 commits into from
Jan 12, 2023

Conversation

Lyd1aCla1r3
Copy link
Contributor

No description provided.

@Lyd1aCla1r3 Lyd1aCla1r3 requested review from nshaw and jyunmitch January 9, 2023 19:43
@@ -31,7 +31,7 @@ Keycloak authorizes microservices using clients and roles. Authorizations are st

Below are the steps to grant a user one or more roles for a specific client. This controls permissions when configuring the microservice. Note: when a microservice is installed in Entando, a corresponding client (and set of roles) is created per its plugin definition.

1. [Login to your Keycloak instance](#logging-into-your-keycloak-instance)
1. [Login to Keycloak](#logging-into-your-keycloak-instance), which for non-external Keycloak instances is [the base URL of your running Entando application](../getting-started/README.md#configure-access-to-your-cluster) followed by `/auth/`, e.g. http://YOUR-HOST-NAME/auth. In a standard Entando installation, the base URL can be verified with `kubectl get ingress/default-sso-in-namespace-ingress`.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we want to keep it simple, I think kubectl get ingress or kubectl describe ingress works too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nshaw do you have a preference for this command?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Lyd1aCla1r3 The specific ingress that maps in the /auth/ path is the default-sso-in-namespace-ingress. I think the extra information is good so I'd probably keep what we have here, at the risk of it aging over time.

@nshaw
Copy link
Member

nshaw commented Jan 9, 2023

@Lyd1aCla1r3 Looks good, just need to add in v7.1 as well.

@Lyd1aCla1r3 Lyd1aCla1r3 merged commit ca04d8c into main Jan 12, 2023
@nshaw nshaw deleted the ENDOC-640 branch May 23, 2023 13:45
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

Successfully merging this pull request may close these issues.

3 participants