-
Notifications
You must be signed in to change notification settings - Fork 66
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
Enable basic auth file user store support #862
Enable basic auth file user store support #862
Comments
Is a mapping type the best choice for this use case? If you use a mapping value, the # 1) Inline table version
[auth.users]
alice = { password ="password1", scopes="scope1"}
bob = { password ="password2", scopes="scope1"}
# 2) Standard table version
[auth.users.alice]
password="password1"
scopes="scope1"
[auth.users.bob]
password="password2"
scopes="scope1" How about using a Ballerina [[auth.users]]
username = "alice"
password="password1"
scopes="scope1"
[[auth.users]]
username = "bob"
password="password2"
scopes="scope1"
# With inline tables
[auth]
users = [ { username = "Alice", password ="password1", scopes="scope1"},
{ username = "Bob", password ="password2", scopes="scope1"} ] Here is the Ballerina syntax:
|
Yes. I am +1 for the Ballerina IMO, it would be better to support the type AuthInfo record {
readonly string username;
string password;
string[] scopes?;
};
configurable table<AuthInfo> key(username) & readonly users = ? |
The fix is reverted by ballerina-platform/module-ballerina-auth#92. |
Need to enable "basic auth file user store" support after Swan Lake alpha which was disabled due to a limitation of
configurable
feature does not support for mapping types.This was disable by the PRs.
Related PRs:
The text was updated successfully, but these errors were encountered: