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

Use Azure Managed Identities for authentication to other resources #1379

Open
bramverdonck opened this issue Oct 3, 2024 · 1 comment
Open
Assignees
Labels
enhancement New feature or request

Comments

@bramverdonck
Copy link

Is your feature request related to a problem? Please describe.
We're currently in the process of implementing an LDES architecture at a client in their Azure ecosystem.
For security reasons, we would need to use Managed Identities for secure authentication between the LDIO workbench and an azure sql database for PostgreSQL. Ideally, we can manage the authentication using managed identities

Describe the solution you'd like
We can use Managed Identities / App registrations as a way of authentication instead of hardcoding values or sending plain text connection secrets.

Describe alternatives you've considered
/
Additional context
We would like to implement the complete LDES architecture before year's end (in production)

@bramverdonck bramverdonck added the enhancement New feature or request label Oct 3, 2024
@sandervd
Copy link
Contributor

sandervd commented Oct 8, 2024

Hi Bram,

As this isn't something that we need ourselves at the moment, so this isn't something that we'll be implementing anytime soon. If you create a PR that is compatible with the current code, we'll make sure to review it.

It certainly helps if you describe the proposed solution in detail before opening a PR, this avoids rework on your side.

@sandervd sandervd assigned sandervd and bramverdonck and unassigned sandervd Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants