Closed. This question is not about programming or software development. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 months ago.
This post was edited and submitted for review 3 months ago and failed to reopen the post:
Original close reason(s) were not resolved
Improve this question
We want to store users in the open source FoxIDs IdP combined with users located in Azure AD.
Is it possible to provide an additional IdP (Azure AD) for the FoxIDs IdP without the service provider (website) having to know that it is to ways login?
The setup:
We have a website using SAML 2.0 that interfaces towards FoxIDs.
Users are redirected to FoxIDs login.
Based on what email the user enters, they are (depending on the domain) either: Redirected to Azure AD or stays on FoxIDs where they authenticated with username/password.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 days ago.
Improve this question
I'm a bit confused because I read a lot about authentication in React apps and NestJS app with using Passport, passport-azure-ad, msal-react with two different Azure AD Apps. Where I authenticate the user in the React app and msal-lib and then using JWT to authenticate against my NestJS api backend.
But is that really necessary and best prectice if my react app is served through my NestJS app and the user auth via Passport to get the static files?
I plan to host the whole app (frontend and backend) later in an Azure App Service.
Hope you can give me hints how to setupg auth in my app.
BR
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 days ago.
Improve this question
We develop an app that sends mail on behalf of a user when some event occurs. We have SPA (react) that the user can log in with several emails and choose the sender depending on which event has occurred. Then, when the event occurs the server (python - fastAPI) side sends mail on behalf of the user who logged in from the spa (or the chosen one from a list). We succeeded to do it with gmail but we faced problems with azure ad.
Thats the steps we want to achieve:
The user connects to his Microsoft account from SPA (react).
The SPA sends the tokens to the server (fastApi).
The server requests the graph api for refreshToken.
We tried to use msal in the front-end but we only get access token because thats SPA. how can we obtain what we want to achieve?
We also tried to use the accessToken from back-end as a Web platform.
Is there a better way to do it?
Our application uses OKTA. We have to login to the OKTA portal,
I am used Web(HTTP/HTML).
Does LoadRunner support the scripting and handling of applications that use Okta authentication as part of their login protocol? If so, can anyone point me to a guide/documentation that explains how this is handled?
There is a similar question asked on Micro Focus LoadRunner Professional community forum.
You can check for update there.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I have django-rest-framework backend and React frontend.
I want to use SSO (Single Sign-On).
JWT token will be used for registration and authentification.
What is the best approach for registration?
Using front-end in this case will make two requests to SSO for registration (getting JWT) and to back-end with data.
Front-end make only one request to back-end with data and registration will be there.
JSON webtokens works of registration.
there is an option to add Refresh tokens with JSON tokens but needs more work, secure
tokens against XSS attacks, then u r good to go :)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I believe Azure AD B2C is great and will lift a lot of weight for many devs. I have a few questions as I stubbornly try to get it in production on my personal apps as soon as possible.
Is it ok to use azure ad b2c with angular js as long as we are ok with the id_token expiring every hour and have to make users go back to AAD everytime?
If not, is it ok to just use the graph api with angular js? (might be a redundant question)
If our need is to just return claims and an id_token, Can we use azure ad b2c in production?
Any help/source code greatly appreciated.
1 -2 When the token expires it can be auto renewed without the user having to re-enter their credentials on Azure.
I don't see any reason why you shouldn't use Azure B2c in production. It is in general availability and production ready.
As Azure AD B2C is an implementation of Open ID you may benefit from getting an overview of Open ID. There are may resources on the internet. Here is a quick overview video.
https://www.youtube.com/watch?v=BdKmZ7mPNns