Ziti login -f admin1@gmail.com.json returns unAuthorized

i am running openziti/quickstart v2.0.0.

when i exec inside ziti-controller and do zitiLogin(logs me in as default admin, username/password auth), i can list identities with ziti edge list identities and it works.

when i cp a identity json file and do ziti login -f admin1@gmail.com.json, and then try to list identities, i get error:

ziti@9ec4b4bf57c3:/persistent$ ziti login -f ./admin1@gmail.com.json
Saving identity 'default' to /home/ziti/.config/ziti/ziti-cli.json
ziti@9ec4b4bf57c3:/persistent$ ziti edge list identities
Error: error listing https://ziti-edge-controller:443/edge/management/v1/identities in Ziti Edge Controller. Status code: 401 Unauthorized, Server returned: {
"error": {
"code": "UNAUTHORIZED",
"message": "The request could not be completed. The session is not authorized or the credentials are invalid",
"requestId": "M8iZRloe1"
},
"meta": {
"apiEnrollmentVersion": "0.0.1",
"apiVersion": "0.0.1"
}
}

error listing https://ziti-edge-controller:443/edge/management/v1/identities in Ziti Edge Controller. Status code: 401 Unauthorized, Server returned: {
"error": {
"code": "UNAUTHORIZED",
"message": "The request could not be completed. The session is not authorized or the credentials are invalid",
"requestId": "M8iZRloe1"
},
"meta": {
"apiEnrollmentVersion": "0.0.1",
"apiVersion": "0.0.1"
}
}
ziti@9ec4b4bf57c3:/persistent$

admin1@gmail.com is a ziti admin.

my goal is to delete default Admin user(created by ziti ziti-controller-init-container), and auth using certs only(no username/password at all).

Hi @CarlosHleb, this seems like a regression. I'll file a bug and get it fixed. Thanks for letting us know. I'll follow up with a bug when i log it.

Hello,

Its been 8 days. Can you give us some kind of timeline when this can be fixed and new docker openziti/quickstart image can be pushed?

Timeline - dunno. I'll see if I can get this fixed this week or next week (I'll try to get to it as soon as possible so maybe sooner)... As for the quickstart not publishing that's a wholly different issue. I saw you mention that on a different thread. I'll have to look into why those are not publishing... I'll do that too...

These fixes should go out in the next point release of 2.0.x and 2.1.x. cheers. You can pull main and build it if you want to test it out yourself. Oh man, I see my msg and a release literally just crossed paths.. So prolly 2.0.7+ will have the fix if you want the 2.0.x line.