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

Identify and configure necessary accesses for Profile using Workload identity #141

Closed
7 tasks done
Tracked by #486
SandGrainOne opened this issue Apr 4, 2024 · 0 comments
Closed
7 tasks done
Tracked by #486
Assignees
Labels
kind/user-story Used for issues that describes functionality for our users.

Comments

@SandGrainOne
Copy link
Member

SandGrainOne commented Apr 4, 2024

Description

The Profile application should be updated to access azure resources through workload identity.

Identified resources:

  • Read access to Platform KeyVault

Tasks

  • Configure the necessary accesses through workload identity (helm chart)
    • Service account
    • Azure AD configuration?
  • Update the code to no longer use the kvSettings to access the KeyVault
  • QA
  • Manual tests

Acceptance criteria

  • Profile can access the platform key vault without the explicitly shared credentials.

Tasks

@SandGrainOne SandGrainOne transferred this issue from Altinn/altinn-platform Apr 4, 2024
@SandGrainOne SandGrainOne changed the title Identify and configure necessary accesses for Profile Identify and configure necessary accesses for Profile using Workload identity Jun 10, 2024
@acn-sbuad acn-sbuad added the kind/user-story Used for issues that describes functionality for our users. label Jun 11, 2024
@khanrn khanrn self-assigned this Jul 8, 2024
khanrn added a commit that referenced this issue Jul 11, 2024
* wi-profile: giving access to platform keyvault

* string interpolation removed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story Used for issues that describes functionality for our users.
Projects
None yet
Development

No branches or pull requests

4 participants