-
Notifications
You must be signed in to change notification settings - Fork 20
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
Integrate auth logic into mlflow, aim, admin, chooser parts #1051
Integrate auth logic into mlflow, aim, admin, chooser parts #1051
Conversation
…ooser` parts. move `/namespaces/current` and `namespaces/list` endpoints to `chooser` part.
if authToken == nil || !authToken.HasUserAccess(namespace.Code) { | ||
return ctx.Status( | ||
http.StatusNotFound, | ||
).JSON( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is chooser, maybe we should provide plain text response instead of JSON? or, ideally, HTML.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, plain test response is reasonable. rendering html
inside the middleware
not a good approach I think. probably in such cases works well forwarding
to error
page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so I think now we can just send something plain.
…dsuhinin/user-auth-part-2
This is 2/2 part. Whats inside the box:
mlflow
,aim
,admin
,chooser
parts.