What should be the base path for the Gate application?

[brionmario]

ATM, the base path for the gate application is signin (ex: https://localhost:8090/signin?xxx).

This poses a problem when we try to serve signup related UIs from the portal.

What should be the ideal base path for this application?

IMO, it should be generic so that we can serve signin, signup & recovery from the same application.

ex:

• https://localhost:8090/<BASEPATH>/signin
• https://localhost:8090/<BASEPATH>/signup
• https://localhost:8090/<BASEPATH>/recover

[darshanasbg]

+1 for the proposed change..

But are you suggesting to keep the base path configurable?

[brionmario]

But are you suggesting to keep the base path configurable?

That as well.
But we need to decide on the default.

[brionmario]

@jeradrutnam FYI

Shall we decide on a default?

[brionmario]

I'm more infavor towards accounts, maybe since this is more familiar , but gate is also fine as a fresh idea :)

[brionmario]

But, lets go ahead with gate...

[darshanasbg]

If we expose every public facing endpoints that accessed through browser (which includes oauth2 authorize endpoint) through this portal the gate name suits better. If this is for the portal that used for only to show the login, registration, self service UIs, the accounts suits better.

Still, lets go ahead with the gate as default path for the 0.12.0 release and revisit this in the next.

[brionmario]

+1

[brionmario]

cc: / @mevan-karu

This will be a breaking change.

[brionmario]

Changed with #762

New Paths:

• https://localhost:8090//signin
• https://localhost:8090//signup