You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by jeffrson March 28, 2023
Hi,
I have a private registry, publicly accessible, but requires user account credentials.
Now I'm setting up another registry, which should use my private registry (this is in a company which usually has all clients protected, but allows access from a special endpoint to the outside). This second registry of course needs to authenticate against the former private registry.
How can this be done? I know, in "Uplinks" there are "auth" settings. These settings work fine. Unfortunately, I set up my logins to expire after about 3 months, so I would need to update the auth token (locally in this company) and restart Verdaccio. A lot may go wrong here.
Any better idea? Real copy of auth request (bearer and basic) will probably not work, because every instance has its own key for signing afaict.
The text was updated successfully, but these errors were encountered:
Discussed in https://github.com/orgs/verdaccio/discussions/3708
Originally posted by jeffrson March 28, 2023
Hi,
I have a private registry, publicly accessible, but requires user account credentials.
Now I'm setting up another registry, which should use my private registry (this is in a company which usually has all clients protected, but allows access from a special endpoint to the outside). This second registry of course needs to authenticate against the former private registry.
How can this be done? I know, in "Uplinks" there are "auth" settings. These settings work fine. Unfortunately, I set up my logins to expire after about 3 months, so I would need to update the auth token (locally in this company) and restart Verdaccio. A lot may go wrong here.
Any better idea? Real copy of auth request (bearer and basic) will probably not work, because every instance has its own key for signing afaict.
The text was updated successfully, but these errors were encountered: