Skip to content
This repository was archived by the owner on Jun 23, 2023. It is now read-only.

Conversation

peppelinux
Copy link
Member

@peppelinux peppelinux commented May 15, 2021

this PR helped understanding a weakness in the general configuration manager, used to put default capabilities and get it in provider-discovery json response BUT these paramenters doesn't really changed the endpoints behaviour.

With this approach I got several benefits, also did:

  • chore: general refactor
  • feat: WEAK algorithms makes a warning message in logs

this commit addresses #22

- chore: general refactor
- feat: WEAK algorithms makes a warning message in logs

this commit addresses #22
@peppelinux peppelinux requested a review from rohe May 15, 2021 12:23
_info[attr] = default_val
elif "signing_alg_values_supported" in attr:
_info[attr] = assign_algorithms("signing_alg")
if "none" in _info[attr]:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@roland this is the only warning I'd tell you.
In you previour approach only if attr == "token_endpoint_auth_signing_alg_values_supported" the none value has been removed. I didn't understad this condition, so I remove none at every occourrence.

Feel free to revert and explain why that rule is only valid for token_endpoint_auth_signing_alg_values_supported

@rohe rohe merged commit b7d3914 into develop May 16, 2021
@rohe rohe deleted the construct_endpoint_info branch May 16, 2021 06:46
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants