Mailing List Archives
Authenticated access
|
|
|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] SEC_CREDENTIAL_STORER and the oauth credmon
- Date: Fri, 25 Jul 2025 19:02:45 +0000
- From: Jaime Frey <jfrey@xxxxxxxxxxx>
- Subject: Re: [HTCondor-users] SEC_CREDENTIAL_STORER and the oauth credmon
I donât believe we have a supported way to do the credential management workflow that you want: job submitter provides the refresh token and the oauth credmon handles refreshing.
- Jaime
> On Jul 24, 2025, at 5:09âPM, David Schultz <david.schultz@xxxxxxxxxxxxxxxx> wrote:
>
> Hi,
>
> Asking about oauth tokens when submitting jobs, is there a way to use the SEC_CREDENTIAL_STORER to create a refresh token, then let the oauth credmon do the refreshes? From the testing I've done, as soon as I define the CLIENT_ID that the credmon needs, that precludes using SEC_CREDENTIAL_STORER for that oauth provider. Note that I specifically do not want the default oauth website functionality, as that won't generate the correct token.