cloudfoundry / cloudfoundry/uaa

Avoid necessity to configure SAML SP in UAA

Open
#2,741 6 comments 1 reaction 1 assignee View on GitHub

@strehle is already working on this.

Since Dec 5, 2024.

unscheduled
Dominant language
Java
Stars
1.6k
Forks
844
Avg merge
2d 5h
Merged PRs (30d)
27

Description

What version of UAA are you running?

76.30

How are you deploying the UAA?
  • using cf-deployment
What did you do?

Usage of UAA without the need of SAML.

What did you expect to see? What goal are you trying to achieve with the UAA?

No need to configure SAML SP (including private key + certificate etc.) in uaa.yml.

What did you see instead?

SAML SP configuration (private key + certificate etc.) is required in uaa.yml. Otherwise, UAA will not startup.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.