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

Third party Identity Provider Integration #59

Open
sfmskywalker opened this issue Jan 24, 2024 · 3 comments
Open

Third party Identity Provider Integration #59

sfmskywalker opened this issue Jan 24, 2024 · 3 comments

Comments

@sfmskywalker
Copy link
Member

With one or some of the following providers:

  • Azure AD
  • Auth0
  • Identity Server 4
  • OpenIddict
  • etc...
@sfmskywalker
Copy link
Member Author

See also elsa-workflows/elsa-core#4814 (reply in thread) for additional context.

@adamfisher
Copy link

I'm pretty much stuck on the Azure AD integration. What we did for Elsa v2 doesn't appear to work either.

@zuntio
Copy link

zuntio commented Jun 17, 2024

Here is my 5 cents for this topic. Azure AD / MS Entra ID specifically.

elsa-workflows/elsa-core#4814 (comment)

Biggest issue was that when implementing custom functionality, I could not use the built-in way of storing tokens using jsInterop resulting in exceptions. How come it actually works in Elsa Studio at all, when jsInterop should not work within OnInitializeAsync? :) This bugs be because storing tokens server side is not really good practice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants