fixed cross-reference
This commit is contained in:
parent
a335c4544c
commit
824bceaf3e
1 changed files with 17 additions and 6 deletions
|
@ -75,9 +75,20 @@ keys will no longer be active and can only be used for verifying signatures.
|
|||
|
||||
==== Disabling keys
|
||||
|
||||
Locate the keypair in `Active` then click on the provider in the `Provider` column. This will take you to the
|
||||
configuration screen for the key provider for the keys. Click on `Enabled` to turn it `OFF`, then click on `Save`. The
|
||||
keys will no longer be enabled.
|
||||
.Procedure
|
||||
. Select the realm in the admin console.
|
||||
. Click Realm settings.
|
||||
. Click the *Keys* tab.
|
||||
. Click the *Active* tab.
|
||||
. Click the provider of the key you want to make passive.
|
||||
. Toggle *Enabled* to *OFF*.
|
||||
. Click *Save*.
|
||||
|
||||
==== Compromised keys
|
||||
|
||||
{project_name} has the signing keys stored just locally and they are never shared with the client applications, users or other
|
||||
entities. However if you think that your realm signing key was compromised, you should first generate new keypair as described above and
|
||||
then immediately remove the compromised keypair.
|
||||
|
||||
Alternatively, you can delete the provider from the `Providers` table.
|
||||
|
||||
|
|
Loading…
Reference in a new issue