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

[Bug]: Connecting to Milvus with authentication, receiving gRPC error #37714

Closed
1 task done
strugc opened this issue Nov 15, 2024 · 4 comments
Closed
1 task done

[Bug]: Connecting to Milvus with authentication, receiving gRPC error #37714

strugc opened this issue Nov 15, 2024 · 4 comments
Assignees
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@strugc
Copy link

strugc commented Nov 15, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

No response

Current Behavior

Set common.security.authorizationEnabled to true in the Milvus configuration file milvus.yaml

Error code:
raise _InactiveRpcError(state) # pytype: disable=not-instantiable
grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
status = StatusCode.UNAUTHENTICATED
details = "auth check failure, please check username and password are correct"
debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"auth check failure, please check username and password are correct", grpc_status:16, created_time:"2024-11-15T07:55:36.6657145+00:00"}"

Try setting reset password
common:
security:
superUsers: root, foo

Restart docker, Running the script still reports an error gRPC

from pymilvus import MilvusClient
client = MilvusClient(
uri='http://locahost:19530',
token="root:Milvus"
)
print(client.has_collection("test_collection"))

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@strugc strugc added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 15, 2024
@SimFG
Copy link
Contributor

SimFG commented Nov 15, 2024

Which version of milvus and pymilvus are you using? Can you also show me all the values ​​under common.security in the milvus yaml file?

@yanliang567
Copy link
Contributor

/assign @strugc

@yanliang567 yanliang567 added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 15, 2024
@xiaofan-luan
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Environment

No response

Current Behavior

Set common.security.authorizationEnabled to true in the Milvus configuration file milvus.yaml

Error code: raise _InactiveRpcError(state) # pytype: disable=not-instantiable grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with: status = StatusCode.UNAUTHENTICATED details = "auth check failure, please check username and password are correct" debug_error_string = "UNKNOWN:Error received from peer {grpc_message:"auth check failure, please check username and password are correct", grpc_status:16, created_time:"2024-11-15T07:55:36.6657145+00:00"}"

Try setting reset password common: security: superUsers: root, foo

Restart docker, Running the script still reports an error gRPC

from pymilvus import MilvusClient client = MilvusClient( uri='http://locahost:19530', token="root:Milvus" ) print(client.has_collection("test_collection"))

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

you need later milvus version, better to be 2.4.15.

Older milvus don't support token like user:passwod but you need to pass username and password seperatly

@yanliang567 yanliang567 removed their assignment Nov 18, 2024
Copy link

stale bot commented Dec 20, 2024

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Rotten issues close after 30d of inactivity. Reopen the issue with /reopen.

@stale stale bot added the stale indicates no udpates for 30 days label Dec 20, 2024
@stale stale bot closed this as completed Dec 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug stale indicates no udpates for 30 days triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
None yet
Development

No branches or pull requests

4 participants