Skip to content
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

Import config auth failed #8833

Closed
zrfan2016 opened this issue Jul 30, 2022 · 5 comments
Closed

Import config auth failed #8833

zrfan2016 opened this issue Jul 30, 2022 · 5 comments
Labels
area/Nacos console Related to Nacos consle kind/bug Category issues or prs related to bug.
Milestone

Comments

@zrfan2016
Copy link

Describe the bug
A clear and concise description of what the bug is.

when auth enable and user don't have the default namespace authority, user import configuration will auth failed

Expected behavior
A clear and concise description of what you expected to happen.

user can import configuration into the namespace he has permission

Actually behavior
A clear and concise description of what you actually to happen.

when auth enable and user don't have the default namespace authority, user import configuration will auth failed

How to Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See errors

Desktop (please complete the following information):

  • OS: [e.g. Centos]
  • Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
  • Module [e.g. naming/config]
  • SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]
  • Version 2.0.2

Additional context
Add any other context about the problem here.

I have read the code of authority authentication. You can add the parameter tenant in the request, and this problem can be solved .

@chenhao26-nineteen
Copy link
Collaborator

Describe the bug A clear and concise description of what the bug is.

when auth enable and user don't have the default namespace authority, user import configuration will auth failed

Expected behavior A clear and concise description of what you expected to happen.

user can import configuration into the namespace he has permission

Actually behavior A clear and concise description of what you actually to happen.

when auth enable and user don't have the default namespace authority, user import configuration will auth failed

How to Reproduce Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See errors

Desktop (please complete the following information):

  • OS: [e.g. Centos]
  • Version [e.g. nacos-server 1.3.1, nacos-client 1.3.1]
  • Module [e.g. naming/config]
  • SDK [e.g. original, spring-cloud-alibaba-nacos, dubbo]
  • Version 2.0.2

Additional context Add any other context about the problem here.

I have read the code of authority authentication. You can add the parameter tenant in the request, and this problem can be solved .

Please provide your version of Nacos client and server.

@zrfan2016
Copy link
Author

Server 2.0.2 @chenhao26-nineteen

@chenhao26-nineteen
Copy link
Collaborator

chenhao26-nineteen commented Aug 1, 2022

Server 2.0.2 @chenhao26-nineteen

@i will solve it@

@zrfan2016
Copy link
Author

Should the user be given default namespace permission or should the tenant parameter be added
@chenhao26-nineteen

@chenhao26-nineteen
Copy link
Collaborator

Should the user be given default namespace permission or should the tenant parameter be added @chenhao26-nineteen

add tenant field verification

@KomachiSion KomachiSion added area/Nacos console Related to Nacos consle kind/bug Category issues or prs related to bug. labels Aug 1, 2022
@KomachiSion KomachiSion added this to the 2.1.1 milestone Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/Nacos console Related to Nacos consle kind/bug Category issues or prs related to bug.
Projects
None yet
Development

No branches or pull requests

3 participants