token-based auth not supported

[yoshikakbudto]

seems like only basic auth supported.
It would be nice to have a more robust token-based auth support

[andrey-pohilko]

Is your issue resolved by your PR?

[yoshikakbudto]

there re no my code covered by tests yet 26 февр. 2018 г. 21:25 пользователь "andrey-pohilko" < notifications@github.com> написал:

…

Is your issue resolved by your PR? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#40 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJ2nKkluAEkYfOmZb56BnOfm1V9pfMEiks5tYtsJgaJpZM4SCBNW> .

[christian-2]

I would also like to see support of token-based authentication. Context: private Docker registry with OpenID Connect (via Keycloak) for authentication.

[andrey-pohilko]

you can help in adding this feature if you provide some test environment with this kind of token auth. this project is developed in our spare time and we don't have much of this (spare time) to run through all possible combinations of use cases

…

On Fri, May 17, 2019 at 4:45 PM christian-2 ***@***.***> wrote: I would also like to see support of token-based authentication. Context: private Docker registry with OpenID Connect (via Keycloak) for authentication. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#40?email_source=notifications&email_token=AECNB66X33U3VWTMVBEMLILPV2EEHA5CNFSM4EQICNLKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVUNQKQ#issuecomment-493410346>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AECNB6ZEOAIN2ONL5PRUQ2TPV2EEHANCNFSM4EQICNLA> .

[ghmer]

I would also like to see support of token-based authentication. Context: private Docker registry with OpenID Connect (via Keycloak) for authentication.

actually, this seems to be working with the current version of the script. Just make sure to use the --auth-method=GET parameter and it should work with your keycloak IdP.