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
We request coordination between DE developers and glideinwms developers to describe the procedure
of what it will take to get the Decision Engine to acquire and generate SciTokens for glideinwms submissions
to remote sites, and IDTokens to authenticate the glideins to the hepcloud user pools.
Decision Engine runs the latest glideinwms frontend libraries but it is not clear if other things
are needed to make it work.
If modifications to the code are necessary, this should be considered a request to make them,.
The drop dead time by which this must be done, is when OSG transitions the hosted-CE's in front of the
XSEDE resources to be tokens only. This may be happening as early as 2Q 2022.
The text was updated successfully, but these errors were encountered:
I am now configuring fermicloud435 (DE 1.7.4) and fermicloud467 (DE 2.0.2) to start using idtokens and SciTokens.. thus
far fermicloud435 has been able to talk to the factory using idtokens..
We request coordination between DE developers and glideinwms developers to describe the procedure
of what it will take to get the Decision Engine to acquire and generate SciTokens for glideinwms submissions
to remote sites, and IDTokens to authenticate the glideins to the hepcloud user pools.
Decision Engine runs the latest glideinwms frontend libraries but it is not clear if other things
are needed to make it work.
If modifications to the code are necessary, this should be considered a request to make them,.
The drop dead time by which this must be done, is when OSG transitions the hosted-CE's in front of the
XSEDE resources to be tokens only. This may be happening as early as 2Q 2022.
The text was updated successfully, but these errors were encountered: