Added install instructions for EAP adapters via RPM (KEYCLOAK-5598) #232
Conversation
Build completed ok (commit 44861c3) Full Log |
$ {EAP_HOME}/bin/jboss-cli.sh -c --file=${EAP_HOME}/bin/adapter-install-saml.cli | ||
---- | ||
|
||
Your installation is complete. Start the EAP server. |
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.
EAP should be started before the first jboss-cli.sh
command, because those would fail when EAP's stopped
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.
Thanks for catching that.
|
||
. If you are already subscribed to another JBoss EAP repository, you must unsubscribe from that repository first. | ||
|
||
Using Red Hat Subscription Manager, subscribe to the JBoss EAP 7.0 repository using the following command. Replace <RHEL_VERSION> with either 6 or 7 depending on your Red Hat Enterprise Linux version. |
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.
We also have EAP 6 adapters, would be a nice idea to add them to docs
These are repos for eap6 and eap7 respectively
jb-eap-6-for-rhel-${RHEL_VERSION}-server-rpms
jb-eap-7-for-rhel-${RHEL_VERSION}-server-rpms
and package names for eap6 look about the same:
eap6-keycloak-adapter
eap6-keycloak-saml-adapter
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.
Ooh, thanks! I didn't know these existed.
I have added install instructions for EAP 6 from RPMs and I removed the instructions to stop/start the server. |
Build completed ok (commit 055cbca) Full Log |
looks good to me, thank you! |
yay. just yay. ;-) |
Nice one @matthewhelmke. I'm impressed and beyond pleased that we now have a writer that understands the technical stuff :) |
@Wyvie Thanks for reviewing |
From this issue. Ready for review.