You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of expected behavior and the observed behavior
Expected behavior
#5386 adds the ability to authenticate user names and optionally user paths in a Panel app. If a user does not create an authorize_callback method that takes two parameters, then the new optional user path checks for authentication should be ignored.
Observed behavior
A follow up comment #5386 (comment) from @el-abcd indicates that the feature errors when an authorize_callback object only has one parameter. @maximlt also confirmed the bug in the conversation.
Complete, minimal, self-contained example code that reproduces the issue
This commit adds some extra logic, and error messages around user
authentication with a user supplied `authorize_callback` method.
- Adds more messaging around the `RuntimeError` when an error occurs
during authorization checks.
- Adds messaging to a user attempting access a path they do not have
access to.
- Adds logic to ensure if an `authorize_callback` has only 1 parameter,
it does not cause a `RuntimeError`.
Resolvesholoviz#5503
ALL software version info
Description of expected behavior and the observed behavior
Expected behavior
#5386 adds the ability to authenticate user names and optionally user paths in a Panel app. If a user does not create an
authorize_callback
method that takes two parameters, then the new optional user path checks for authentication should be ignored.Observed behavior
A follow up comment #5386 (comment) from @el-abcd indicates that the feature errors when an
authorize_callback
object only has one parameter. @maximlt also confirmed the bug in the conversation.Complete, minimal, self-contained example code that reproduces the issue
Run the apps via the command line
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: