commit
57ac824049
2 changed files with 21 additions and 0 deletions
|
@ -99,3 +99,5 @@
|
|||
... link:topics/enforcer/authorization-context.adoc[Obtaining the Authorization Context]
|
||||
|
||||
... link:topics/enforcer/js-adapter.adoc[JavaScript Integration]
|
||||
|
||||
... link:topics/enforcer/https.adoc[Setting up TLS/HTTPS]
|
19
topics/enforcer/https.adoc
Normal file
19
topics/enforcer/https.adoc
Normal file
|
@ -0,0 +1,19 @@
|
|||
[[_enforcer_filter_using_https]]
|
||||
== Setting Up TLS/HTTPS
|
||||
|
||||
When the server is using HTTPS, make sure your adapter is configured as follows:
|
||||
|
||||
.keycloak.json
|
||||
```json
|
||||
{
|
||||
"truststore": "path_to_your_trust_store",
|
||||
"truststore-password": "trust_store_password"
|
||||
}
|
||||
```
|
||||
|
||||
The configuration above enables TLS/HTTPS to the Authorization Client, making possible to access a
|
||||
{{book.project.name}} Server remotely using the HTTPS scheme.
|
||||
|
||||
[NOTE]
|
||||
Is strongly recommended that you enable TLS/HTTPS when accessing the {{book.project.name}} Server endpoints.
|
||||
|
Loading…
Reference in a new issue