Skip to content
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

Jump to bottom

Hydator Mutator Client Credential #565

Open
schreddies opened this issue Nov 4, 2020 · 3 comments
Open

Hydator Mutator Client Credential #565

schreddies opened this issue Nov 4, 2020 · 3 comments
Labels
feat good first issue help wanted
Milestone
v0.39.0

Comments

@schreddies
Copy link

@schreddies schreddies commented Nov 4, 2020

Is your feature request related to a problem? Please describe.

The hydrator have only Basic auth - see config: https://www.ory.sh/oathkeeper/docs/pipeline/mutator/#configuration-4, however for more flexibility, similiar pre-authorization mechanism could ba added as in the instropsection authenticator handler: https://www.ory.sh/oathkeeper/docs/pipeline/mutator/#configuration-4

Describe the solution you'd like

Adding the whole pre-authorization config to the hydrator will increase possibilities to use hydrator in multiple cases.

Describe alternatives you've considered

Basic auth cannot be used with current config for client credentials for external hydrator service.

Additional context

Can contribute to that.
@aeneasr
Copy link
Member

@aeneasr aeneasr commented Nov 9, 2020

Hey there, I think this is a good idea! We have a call this week anyways, correct? Let's discuss the ideas there!

@aeneasr aeneasr added the feat label Nov 10, 2020
@aeneasr aeneasr added this to the v0.39.0 milestone Nov 10, 2020
@aeneasr aeneasr added good first issue help wanted labels Nov 10, 2020
@schreddies schreddies mentioned this issue Jun 17, 2021
Closed
2 tasks
@github-actions
Copy link

@github-actions github-actions bot commented Sep 21, 2021

I am marking this issue as stale as it has not received any engagement from the community or maintainers in over half a year. That does not imply that the issue has no merit! If you feel strongly about this issue

  • open a PR referencing and resolving the issue;
  • leave a comment on it and discuss ideas how you could contribute towards resolving it;
  • open a new issue with updated details and a plan on resolving the issue.

We are cleaning up issues every now and then, primarily to keep the 4000+ issues in our backlog in check and to prevent maintainer burnout. Burnout in open source maintainership is a widespread and serious issue. It can lead to severe personal and health issues as well as enabling catastrophic attack vectors.

Thank you for your understanding and to anyone who participated in the issue! 🙏✌️

If you feel strongly about this issues and have ideas on resolving it, please comment. Otherwise it will be closed in 30 days!

@github-actions github-actions bot added the stale label Sep 21, 2021
@aeneasr
Copy link
Member

@aeneasr aeneasr commented Sep 21, 2021

Incorrect stalebot detection - this was assigned a milestone.

@github-actions github-actions bot removed the stale label Sep 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feat good first issue help wanted
Projects
None yet
Milestone
v0.39.0
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
@aeneasr @schreddies