-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Credentials Class Refactoring #258
Comments
Using an old, patched version of the Frontend to get IDTOKENs working with my collaborators' Collectors, I happened to use a glideinwms/frontend/glideinFrontendElement.py Line 1138 in 8f1d220
identity = f"gwms-{glidein_site}@${TRUST_DOMAIN}" (where ${TRUST_DOMAIN} is filled in per frontend). As mentioned in the TODO item, it would be nice if there was some more control here in the config.
I suspect allowing the config to template with self.idtoken_subject = self.elementDescript.merged_data.get("IDTokenSubject", "{glidein_site}@{socket.gethostname()}")
...
identity = self.idtoken_subject.format(glidein_site=glidein_site) Then the config could be: <security
security_name="myvo"
idtoken_subject="gwms-{glidein_site}@my-vo-collector.domain"
> I am also already able to set the |
Hi again @BrunoCoimbra! To summarize what we talked about after your fantastic HTC23 presentation:
|
We're refactoring the GlideinWMS Credentials class to improve our code and introduce new features. This issue is used to keep track of our progress and receive requests and suggestions from the project's stakeholders.
New features and improvements
Bug fixes
Work Notes
Tasks
The text was updated successfully, but these errors were encountered: