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

Write installation steps in readme.md #27

Open
fume opened this issue Jun 22, 2022 · 4 comments · May be fixed by #45
Open

Write installation steps in readme.md #27

fume opened this issue Jun 22, 2022 · 4 comments · May be fixed by #45
Assignees
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed

Comments

@fume
Copy link
Collaborator

fume commented Jun 22, 2022

While waiting for the deployment automation (#6), we should write the installation steps in the readme:

  • How to deploy the custom policies in AAD B2C
  • How to deploy and configure the SPIDProxy
  • How to get started with the demo.spid.gov.it environment
@fume fume added documentation Improvements or additions to documentation help wanted Extra attention is needed labels Jun 22, 2022
@fume fume pinned this issue Jun 22, 2022
@MarcoZama MarcoZama linked a pull request Oct 3, 2022 that will close this issue
@asorcinelli
Copy link

Hi, I would like to try your solution. Is it still current? Does the installation documentation not yet exist?

@fume
Copy link
Collaborator Author

fume commented May 14, 2024

Hi @asorcinelli , the solution is still current and widely used. Official docs is still not yet available but you can use the one available in #44

@asorcinelli
Copy link

Hi @fume, thanks for the reply. Yes, I saw the documentation and managed to set up the entire environment. I have a problem, but I don't want to dwell on it here as I don't think it's the right place. Could I contact you somehow and explain the problem? Maybe you can help me. Thank you.

@gicaz
Copy link

gicaz commented Oct 4, 2024

Hi @fume, thanks for all your teamwork. I followed the documentation and configured the entire environment but I have a problem with the response from the proxy to Azure b2c, I always receive an error from b2c: "The service provider is not a valid audience of the assertion". I checked all the available docs and I suppose the problem is on parameters configuration of proxy. I have some doubts about the last section of documentation where you explain how to configure the app settings of Proxy.
This is our configuration:

"Federator": { "MetadataUrl": "https://xxxx.xxxx.it/metadata/metadata.xml", "SPIDEntityId": "https://xxxx.xxxx.it", "CIEEntityId": "https://xxx.xxxxx.it", "EntityId": "https://xxxx.xxxxx.it", //or IdentityExperienceFrameworkAppId??? "FederatorAttributeConsumerServiceUrl": "https://xxxx.b2clogin.com/xxxx.onmicrosoft.com/B2C_1A_TrustFrameworkBase/samlp/sso/assertionconsumer", },
https://xxxx.xxxx.it is the public URL where we deployed your proxy solution.

I suppose the problem is with the EntityId parameter that is involved in the audience settings of the requests.
On the EntityId parameter, I tried to set the IdentityExperienceFrameworkAppId but still did not work

The parameters seem to you, right? Do you notice any mistakes? If you are available, I could contact you or someone on your team to help me to resolve this issue. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants