INTLY-2663 add user sso provision to startup loading task #493
Conversation
aidenkeating
force-pushed
the
INTLY-2663-user-sso
branch
from
fee2985 to
76e91df
Compare
|
@aidenkeating Do you have a cluster running with this already that you could share? I'd like to verify the display of this in SolX. |
|
@tiffanynolan I will set up an environment now for verification |
|
@tiffanynolan @leaannegaffney This is provisioned on my cluster here https://tutorial-web-app-webapp.apps.akeating-242a.openshiftworkshop.com/, the |
| gaStatus: 'GA' | ||
| }, | ||
| rhsso: { | ||
| prettyName: 'Red Hat Single Sign-On (Cluster)', |
There was a problem hiding this comment.
@tiffanynolan this doesn't align with doc at https://integr8ly.github.io/user-documentation/index.html?e=docs/getting-started.adoc#gs-adding-users-proc
but we can adjust as required
There was a problem hiding this comment.
@finp I like how you referred to the 2 instances in the docs as those terms sound more user friendly. Ultimately, I'd like to only show the end-user SSO in the applications list and move the cluster level one to more of an admin screen/settings page. We're not there yet though so we do need some way to easily tell them apart for now.
There was a problem hiding this comment.
@tiffanynolan @finp Just to confirm, should I be changing the naming of this in the web app (and if so, what to)? Or will it be changed in the documentation?
There was a problem hiding this comment.
@aidenkeating my reading of @tiffanynolan comment is to go with what we have. I could add a note to docs if required.
|
@aidenkeating can you also add the user sso to the mock data here: https://github.com/integr8ly/tutorial-web-app/blob/master/server.js#L495 otherwise running the webapp locally won't work |
aidenkeating
force-pushed
the
INTLY-2663-user-sso
branch
2 times, most recently
from
4188aa5 to
62b5ce4
Compare
|
@leaannegaffney Mind taking a look? |
verification: - an integreatly cluster on openshift 3 is required - ensure the user-rhsso clusterserviceclass exists by searching for it on the main page (service catalog) - ensure USER_SSO_URL is set on the managed service broker env var - run this branch locally against the cluster - ensure that the user sso is now also provisioned at startup - ensure the link on the right-hand side works as expected
aidenkeating
force-pushed
the
INTLY-2663-user-sso
branch
from
62b5ce4 to
7ecb10f
Compare
5 participants
verification:
it on the main page (service catalog)
var