https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# general
a
This message was deleted.
f
extraEnv
section in the deploy k8s object
a
As in, use environment variables to configure an external auth provider? No.
f
Yes
Like Azure Ad
a
Not with env variables alone, no.
f
What do you means by the 
env variables alone
? Using the extraEnv section is not enough ? Should I make others request to the API Rancher ?
a
There's only specific options that are influenced by env variables, the only one i've really seen is `CATTLE_TLS_MIN_VERSION`/ 
CATTLE_TLS_CIPHERS
for the docker install version
You should be setting configs like the auth provider using Terraform
You could try and create the underlying auth provider config type directly and post this to the apiserver of the k8s cluster running Rancher, but it's not currently supported
f
Thank you for providing the details. I believe it may be possible to configure extr auth provider using API.
@agreeable-oil-87482 Hi ! I attempted to set up Azure AD authentication with Rancher by making a 
curl
request to the API endpoint 
RANCHER_URL/v3/azureADConfigs/azuread
with the necessary Azure AD configuration details in the request payload. The configuration was successfully activated, but authentication for any Azure AD user is not working as expected.
However, when I configured Azure AD authentication in Rancher using the Rancher UI, I was prompted to authenticate with Azure AD and only upon successful authentication , the activation was successful.
a
Not working as expected in what way?
f
Not working as expected, that means I can't authenticate any AD user
a
Did you configure so any user can login?
Or only explicit users?
f
I think you ask for this attribute 
"accessMode": "unrestricted"
a
Please show what it states in the UI for the Auth config and scope
f
I solved my issue, Thank you a lot I missed to add the follwoing filed in the payload of my PUT Request • Graph Endpoint • Auth Endpoint • Token Endpoint
5 Views
Open in Slack
PreviousNext
Powered by