You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
The first time, I've followed this guideline and bypass the Auth AAD step. It's worked.
But when I on the Auth AAD, It's not worked and got the issue (see image)
When I off the Auth Azure AD, It's worked again.
The text was updated successfully, but these errors were encountered:
Hi @huyenvv90 sorry for the issues you're encountering. Seems like AAD Auth is causing issues. Is your use case being able to access Spektate publicly but with authorization?
@samiyaakhtar how difficult would it be to set up an identity provider in Spektate?
Given an AAD application client id and password we could authenticate. The set up could be as follows:
Configure Spektate with AAD Identity provider credentials for a tenant
Run Spektate in your Kubernetes cluster
Setup an Azure public IP address
Setup an ingress in your Kubernetes cluster using the public IP address (Your can configure such that only Azure Front Door as access)
Setup something like Azure Front Door to route to your backend (exposed public IP address)
This way folks can access Spektate security with authorization using Kubernetes to run the workload.
The first time, I've followed this guideline and bypass the Auth AAD step. It's worked.
But when I on the Auth AAD, It's not worked and got the issue (see image)
When I off the Auth Azure AD, It's worked again.
The text was updated successfully, but these errors were encountered: