-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility to override cloud endpoint #23
Comments
Neat! I'd propose to call this the Nice to have: If possible it would be very neat if we could set |
I introduced Device flow uses different URLs and requires additional parameters so re-configuring it requires more input. Also, with automation, passing |
@f1ames Let's not close this issue just yet and look into As for the extra parameters, maybe we can get away with not making them configurable and work more based on convention / sensible defaults?
Alternative: Origin should point to web appSilly idea but can we configure the web application as origin and the rest is derived from there? Do we want people to enter The GH flow in a screenshot ![]() |
Hmmm, TBH after writing the above I think we should have:
Why?
|
The following options work well together: (1) I'd still hope we can merge origin to the name of the web-app and rely on that as it's easier to use compared to some vaguely internal URLs for the idp and api. Your casual end user will not know anything about them. |
Just to add to recent #23 (comment), as we discussed it with @WitoDelnat F2F briefly - as origin one would pass web app URL (e.g. |
Well, for (1) |
the CLI currently always uses the hosted instance of Monokle Cloud for authenticating keys and retrieving policies - we will need to be able to override the endpoint for use with enterprise deployments of Cloud
The text was updated successfully, but these errors were encountered: