You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@apisix.apache.org by GitBox <gi...@apache.org> on 2021/04/25 07:04:38 UTC
[GitHub] [apisix-dashboard] oldthreefeng opened a new issue #1825: how to create an viewer account for apisix-dashboard?
oldthreefeng opened a new issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825
# Feature request
## Please describe your feature
apisix-dashborad create an admin account by apisix-cm.yaml
but how to create an read only account for dev user?
## Describe the solution you'd like
like apisix X-API-KEY.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] nic-chen commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-826429067
doesn't support this feature now.PR is welcome
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] bisakhmondal commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
bisakhmondal commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-829945422
I can give it a try. @nic-chen how are we planning to support this as of now, through YAML?
Seems like we had a similar conversation a month back :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] starsz commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
starsz commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-836936940
> I can give it a try. @nic-chen how are we planning to support this as of now, through YAML?
> Seems like we had a similar conversation a month back :)
Use YAML is fine. And the front end should also do some work.
You can refer to the config of apisix.
https://github.com/apache/apisix/blob/504cd1b0966880101b3e2582cfb1cf65f23a7863/conf/config-default.yaml#L82-L83
You can send your proposal to the email list. Then we can discuss it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] bisakhmondal commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
bisakhmondal commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-838010435
> https://github.com/apache/apisix/blob/504cd1b0966880101b3e2582cfb1cf65f23a7863/conf/config-default.yaml#L82-L83
This looks good. Thanks for the reference.
> You can send your proposal to the email list. Then we can discuss it.
Sure. I'd be happy to do so :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] nic-chen commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
nic-chen commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-826429067
doesn't support this feature now.PR is welcome
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] bisakhmondal commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
bisakhmondal commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-907135867
Hi @liuxiran, Thanks for sharing the details.
Since Dashboard is for the authenticated users, we definitely can work on top of the authentication framework by storing another field something similar to `"restrict-full-access": bool` in the etcd for each user. The info gets encoded into the existing jwt and passed to the web-ui / CLI on successful signin.
We will add a middleware or modify the existing one to restrict the protected routes (here ig HTTP methods, allow only GET requests, no POST, PUT, PATCH or DELETE).
And for the frontend part, we can cache the info in a react state while receiving the jwt from the backend and perform all sorts of restrictions.
Let me know how this sounds (also @nic-chen @starsz). I would love to hear from you. Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] liuxiran commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
liuxiran commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-900596957
Hi @bisakhmondal , there is a [pr](https://github.com/apache/apisix-dashboard/pull/2010) to refactor our auth framework, hope this can help you
and for a easy way to create a view user, sorry we still do not have plane to do it, and if you have some ideas about it , welcome to send mail to our mail list, thanks a lot
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] liuxiran commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
liuxiran commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-900596957
Hi @bisakhmondal , there is a [pr](https://github.com/apache/apisix-dashboard/pull/2010) to refactor our auth framework, hope this can help you
and for a easy way to create a view user, sorry we still do not have plane to do it, and if you have some ideas about it , welcome to send mail to our mail list, thanks a lot
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [apisix-dashboard] starsz commented on issue #1825: how to create an viewer account for apisix-dashboard?
Posted by GitBox <gi...@apache.org>.
starsz commented on issue #1825:
URL: https://github.com/apache/apisix-dashboard/issues/1825#issuecomment-907801158
> Hi @liuxiran, Thanks for sharing the details.
>
> Since Dashboard is for the authenticated users, we definitely can work on top of the authentication framework by storing another field something similar to `"restrict-full-access": bool` in the etcd for each user. The info gets encoded into the existing jwt and passed to the web-ui / CLI on successful signin.
> We will add a middleware or modify the existing one to restrict the protected routes (here ig HTTP methods, allow only GET requests, no POST, PUT, PATCH or DELETE).
> And for the frontend part, we can cache the info in a react state while receiving the jwt from the backend and perform all sorts of restrictions.
>
> Let me know how this sounds (also @nic-chen @starsz). I would love to hear from you. Thanks.
That sounds good. Maybe we can discuss this in the email list.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: notifications-unsubscribe@apisix.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org