Skip to content

Commit

Permalink
Merge pull request #11496 from justinmcook/WFCORE-3970
Browse files Browse the repository at this point in the history
[WFCORE-3970] Add documentation for the new trust-manager init management operation and add documentation for the existing key-manager init management operation
  • Loading branch information
kabir committed Aug 14, 2018
2 parents 8614939 + 8156264 commit 385e172
Showing 1 changed file with 42 additions and 0 deletions.
42 changes: 42 additions & 0 deletions docs/src/main/asciidoc/_elytron/Using_the_Elytron_Subsystem.adoc
Expand Up @@ -1901,6 +1901,48 @@ To reload a keystore.
/subsystem=elytron/key-store=httpsKS:load
----

[[reinitialize-a-key-manager]]
=== Reinitialize a Key Manager

You can reinitialize a key-manager configured in WildFly from the management CLI.
This is useful in cases where you have made changes in certificates provided by keystore
resource and you want to apply this change to new SSL connections without restarting the server.

If the key-store is file based then it must be loaded first.

[source, bash]
----
/subsystem=elytron/key-store=httpsKS:load()
----

To reinitialize a key-manager.

[source, bash]
----
/subsystem=elytron/key-manager=httpsKM:init()
----

[[reinitialize-a-trust-manager]]
=== Reinitialize a Trust Manager

You can reinitialize a trust-manager configured in WildFly from the management CLI.
This is useful in cases where you have made changes to certificates provided by keystore
resource and you want to apply this change to new SSL connections without restarting the server.

If the key-store is file based then it must be loaded first.

[source, bash]
----
/subsystem=elytron/key-store=httpsKS:load()
----

To reinitialize a trust-manager.

[source, bash]
----
/subsystem=elytron/trust-manager=httpsTM:init()
----

[[check-the-content-of-a-keystore-by-alias]]
=== Check the Content of a Keystore by Alias

Expand Down

0 comments on commit 385e172

Please sign in to comment.