Conversation
modules/ROOT/pages/sync/auth.adoc
Outdated
| [id='{context}_authentication'] | ||
| = Authentication | ||
|
|
||
| The {sync-service} by default do not provide any any authentication and authorization mechanism. |
There was a problem hiding this comment.
@psturc Actually tried to execute this steps and see how long this takes. It's not simple or convenient which made me question entire instruction. pinged @ziccardi to see if we can just get config directly from keycloak server and paste that directly as content to environment variable. If this is working we can document that - possibly instruction will change to 3 simple steps, but it will not include binding.
There was a problem hiding this comment.
This is going to be separate ticket as @ziccardi is out sick.
|
Can we check this again? It's still pretty raw (we can improve it later). |
modules/ROOT/pages/sync/auth.adoc
Outdated
| [id='{context}_authentication'] | ||
| = Authentication | ||
|
|
||
| The {sync-service} by default do not provide any any authentication and authorization mechanism. |
There was a problem hiding this comment.
Perhaps rework this to the following:
By default, {sync-service} does not provide any authentication and authorization mechanism.
modules/ROOT/pages/sync/auth.adoc
Outdated
| * Ensure {keycloak-service} is xref:keycloak/provisioning.adoc[provisioned] | ||
| * Ensure {keycloak-service} is xref:keycloak/coding.adoc[configured] to work with your mobile applications | ||
|
|
||
| == Binding the {sync-service} service to a {keycloak-service} instance |
There was a problem hiding this comment.
Best practice is to captialize headings, except for words like is, a, the, to etc.
Should be:
Binding the {sync-service} Instance to a {keycloak-service} Instance.
There was a problem hiding this comment.
fyi, there's a debate about that style issue, Dara describes the style called Titlecase, more likely we're going with Sentence case, which is what is there currently
modules/ROOT/pages/sync/auth.adoc
Outdated
|
|
||
| == Binding the {sync-service} service to a {keycloak-service} instance | ||
|
|
||
| To benefit from authentication developers need to connect (bind) {sync-service} into {keycloak-service} instance. |
There was a problem hiding this comment.
Minor grammar thing:
To benefit from authentication, developers...
There was a problem hiding this comment.
To implement authentication in your app, you must bind the {sync-service} service with the {keycloak-service} service.
modules/ROOT/pages/sync/auth.adoc
Outdated
|
|
||
| NOTE: The mount path must be set to `/opt/keycloak` for the {sync-service} to be configured to use the secret. | ||
|
|
||
| == Making secret available |
There was a problem hiding this comment.
Again, capitalization. Should probably be:
Making the Secret Available
modules/ROOT/pages/sync/auth.adoc
Outdated
|
|
||
| == Making secret available | ||
|
|
||
| By default secret is not visible to server application |
There was a problem hiding this comment.
Minor grammar thing. Should probably be like this:
By default, the secret is not visible to the server application
modules/ROOT/pages/sync/auth.adoc
Outdated
| == Making secret available | ||
|
|
||
| By default secret is not visible to server application | ||
| To point server to application please add new environment variable: |
There was a problem hiding this comment.
Again just some small grammar stuff,
To point the server to the application, please add a new environment variable:
|
The |
|
After completing the steps, and opening data sync server url on |
|
Will this work with self-signed certs? Should we document it? |
|
The trick for getting this working with self-signed certs is to add |
| include::{partialsdir}/attributes.adoc[] | ||
|
|
||
| = Using the {sync-service} service SDK | ||
| = Using the {sync-service} SDK |
There was a problem hiding this comment.
not the way we refer to SDK in doc, but will fix in post
There was a problem hiding this comment.
Ah.. Really sorry. Missing tons of context here.
The Authentication section is now in Setting up section. Shouldn't it be in it's own section similarly to Monitoring Data Sync Service section?
This is part of the prerequisites (Keycloak setup and running) instruction there explains it and I did not want to copy the content here.
This is canonical documentation ( we will need to get some local machine documentation that will cover self signed certs. |
7f4b5ae to
a3fc127
Compare
|
@darahayes Final review? |
|
Mering to sync branch in order to rebuild, joing articles together |
| o point the server to the application, please add a new environment variable: | ||
|
|
||
| ---- | ||
| KEYCLOAK_CONFIG_FILE= `/opt/keycloak`TODO |
There was a problem hiding this comment.
are we leaving this as is? we could change it to the actual value we are using for now?
There was a problem hiding this comment.
Ups. yeah. TODO needs to be removed. I overlooked that in the rush
|
Its ok I will change it on sync branch. I was too slow reviewing.
…On Wed, 5 Sep 2018 at 11:49, Wojciech Trocki ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In modules/ROOT/pages/sync/auth.adoc
<#403 (comment)>:
> +
+== Making the Secret available to the {sync-service}
+
+* Select *View Secret* on the *Identity Management* details page
+* Select *Add to Application* and select the data-sync-server from the options
+* Select the *Volume* option and enter the following mount path: `/opt/keycloak`
+
+NOTE: The mount path must be set to `/opt/keycloak` for the {sync-service} to be configured to use the secret.
+
+== Making Secret available to application
+
+By default, the secret is not visible to the server application.
+o point the server to the application, please add a new environment variable:
+
+----
+KEYCLOAK_CONFIG_FILE= `/opt/keycloak`TODO
Ups. yeah. TODO needs to be removed. I overlooked that in the rush
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#403 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG9_8-PQa1uD6HAUruIknIyciGs68IgSks5uX6w4gaJpZM4WTKnE>
.
--
STEPHEN COADY
ASSOCIATE SOFTWARE ENGINEER
Red Hat
<https://www.redhat.com/>
Communications House, Cork Road
Waterford City, Ireland X91NY33
scoady@redhat.com IM: scoady
<https://red.ht/sig>
|
Posting for early visibility.