[Bug]: Setting the user name and password does not take effect. #36987
Assignees
Labels
help wanted
Extra attention is needed
Comments
wpx1997-stack
added
kind/bug
|
@wpx1997-stack if the cluster is already initialzied, you can not use config files to change root username. you have to use API to create user and modify existing user's use name. |
if you take a look on this, only if credential is no there can you set the default pasword
|
|
/assign @wpx1997-stack |
|
/unassign |
yanliang567
added
help wanted
|
This is an issue for me too Image: milvusdb/milvus:v2.4.15 Please fix at priority logs: |
|
Even If I start the standalone server with And then later when I try to change the password of the root (by using old password as 'Milvus') |
|
@iamkhalidbashir I think the problem might be you try to change milvus.yaml after instance is already created, which won't work. the default password is a one time config and won't be used if it is already persistent into etcd try to test default passowrd Milvus and see if you can change your password. |
|
The root password is initialized This is my docker-compose deployment file Neither the config.yaml works nor the COMMON_SECURITY_DEFAULTROOTPASSWORD I believe its an issue with attu which doesn't let me sign in when I use the password 'Milvus' for a config.yaml file where defaultRootPassword is set empty |
|
Ok the is not with attu but with milvus |
|
On checking the ectd keys I get following hash stored for user root and when comparing it with an online tool, the hash seems to be correct But still, it doesn't let me sign in |
|
Ok it worked with Basic authorization for the default API key it gave this error (i.e Bearer Token) I think attu might be using the Token Bearer method for which it was getting this error This seems so frustrating as I was struggling for 2 days with this and had to debug the codebase of milvus to resolve this |
|
|
if you take a look here, you request goes to verify api key which is not supported by opensource user. |
|
could you try username password see it working? |
|
Username password works with nodejs sdk and rest api
But it dosent work with attu
*- Khalid*
…On Sat, 9 Nov 2024 at 1:16 AM Xiaofan ***@***.***> wrote:
could you try username password see it working?
—
Reply to this email directly, view it on GitHub
<#36987 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGS5WW2CPZVHKEQUD326MUTZ7UL2NAVCNFSM6AAAAABQFIRJPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRVGY3TQOBXGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
So which means the username password has already work. but for some reason the username:password style is not working |
|
@SimFG could you help on it? |
|
I think the crypto.Base64Decode could be wrongly used at attu and nodejs @shanghaikid |
|
I tested this configuration, everything is working. it works even you put |
|
please make sure your milvus is the latest and attu is the latest as well and test on it. |
|
I found out the issue: in milvus.yaml, the default password can only accept up to 20 characters, like However, for created users, passwords up to |
|
@shanghaikid Is this so strange? I'll verify it later. |
|
Some minor issues were found for this problem:
|
sre-ci-robot
pushed a commit
that referenced
this issue
Nov 26, 2024
- issue: #36987 Signed-off-by: SimFG <[email protected]>
JsDove
pushed a commit
to JsDove/milvus
that referenced
this issue
Nov 26, 2024
…io#37983) - issue: milvus-io#36987 Signed-off-by: SimFG <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Environment
Current Behavior
When using Docker Compose for deployment, setting the username and password does not take effect. The Docker Compose configuration information is as follows:
The milvus.yaml sets the username and password as follows:
When using Attu, I found that I cannot log in.
After entering the Docker container and checking the /milvus/configs/milvus.yaml file, I found that the settings have been successfully applied.
Expected Behavior
No response
Steps To Reproduce
No response
Milvus Log
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: