-
Notifications
You must be signed in to change notification settings - Fork 46
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
SAML example #442
SAML example #442
Conversation
f36c244
to
f429c28
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfdenise I left a few comments even if the MR is already merged....
* Assign the role `user` to the user `demo`. This user will be used to log in the application. | ||
* Create a User named `client-admin`, password `client-admin`, make the password not temporary. This user will be used to create | ||
the SAML client in the keycloak server. It requires more proviledges to interact with the keycloak server and to be able to create the client. | ||
* In the `Client Roles` Select the Client `realm-management`, assign the role `create-client`, `manage-clients` and `manage-realm`. For latest keycloak console, select the `user` role, Click Action/Add associated roles. Then `Filter by clients`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfdenise here it is not clear that the roles need to be assigned to the client-admin
user; perhaps the client-admin
is not needed, in prod docs we say "Assign the roles create-client
, manage-clients
, and manage-realm
to the client-admin
user. " ... we might add a bullet point before "For latest keycloak console, "
<version.wildfly.plugin>4.2.0.Final</version.wildfly.plugin> | ||
<version.wildfly.cloud.galleon.pack>4.0.1.Final</version.wildfly.cloud.galleon.pack> | ||
<jakarta.jakartaee-api.version>10.0.0</jakarta.jakartaee-api.version> | ||
<version.keycloak>22.0.1</version.keycloak> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfdenise can we update to 22.0.3
?
<version.maven.war.plugin>3.3.2</version.maven.war.plugin> | ||
<version.wildfly>28.0.1.Final</version.wildfly> | ||
<version.wildfly.plugin>4.2.0.Final</version.wildfly.plugin> | ||
<version.wildfly.cloud.galleon.pack>4.0.1.Final</version.wildfly.cloud.galleon.pack> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfdenise can we aupdate to 5.0.0.Beta2
or higher?, IIUC this is the version that foxes the issue with the EJB layer...
<maven.compiler.source>11</maven.compiler.source> | ||
<maven.compiler.target>11</maven.compiler.target> | ||
<version.maven.war.plugin>3.3.2</version.maven.war.plugin> | ||
<version.wildfly>28.0.1.Final</version.wildfly> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jfdenise can we udate this one too? last time I used 30.0.0.Beta1
....
No description provided.