Skip to content
This repository has been archived by the owner on Jan 21, 2022. It is now read-only.

Use different clients for SSO and backend access #37

Open
georgi-lozev opened this issue May 30, 2017 · 1 comment
Open

Use different clients for SSO and backend access #37

georgi-lozev opened this issue May 30, 2017 · 1 comment

Comments

@georgi-lozev
Copy link
Contributor

Currently there is only one UAA client used in the dashboard.

From my point of view it makes sense to use one client for the SSO and another for accessing the backend(privisioning). This will lead to better separation of concerns and will allow us to use the automatic registration of the dashboard_client which we've discarded with 45d36ac.

@cf-gitbot
Copy link
Collaborator

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/146279227

The labels on this github issue will be updated when the story is started.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants