Project

General

Profile

Feature #25200

Consider tokens for glidein submission the same way as grid_proxy, ssh keys, ...

Added by Marco Mambelli 5 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
11/13/2020
Due date:
% Done:

0%

Estimated time:
Stakeholders:

OSG

Duration:

Description

Token should simply be a credential type like grid_proxy, ssh_key, username_password, ...
  • it should have a mandatory element (token file, ok to use a name used by the others)
  • there should be no error if that one is used and no proxy
  • the credential matching behavior should remain consistent (composite_type+domain used for matching)

This ticket should do the minimum sw modifications needed to accomplish the above.
A more radical refactoring should happen in Python 3.
See [#24165] for more credential ideas and the direction in v3.9


Related issues

Related to GlideinWMS - Feature #24165: Refactor credential handlingNew03/10/2020

History

#1 Updated by Marco Mambelli 5 months ago

#2 Updated by Marco Mambelli 5 months ago

  • Target version changed from v3_7_2 to v3_7_3

#3 Updated by Dennis Box 2 months ago

At least partially resolved by #25504

#4 Updated by Dennis Box about 2 months ago

  • Status changed from New to Feedback

These requirements were all met implementing feedback to #25504

#5 Updated by Dennis Box about 1 month ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF