Hi all, I have my pactflow on-prem setup in PKS. C...
# pactflow
p
Hi all, I have my pactflow on-prem setup in PKS. Currently it is in Demo-auth mode. I wanted to know what changes I would need to do to make AUTHENTICATION ENABLED. I have gone through docs and configurations of SAML-Pactflow doc. Do I just need to add all configurations in below image (PKS Deployment script) ? (By all config i mean all variables starting with Prefix PACTFLOW_SAML_)
m
That’s correct. You don’t necessarily need all of the variables, are some (e.g. if the metadata URL is provided) automatically determine others. see https://docs.pactflow.io/docs/on-premises/authentication/saml
👀 1
Please do ensure you update some of these, e.g. The encryption key, admin key and secrets. requiring https should also be set to
true
in real life. I also hope you can update the postgres database from the default username/password 😱
👍 1
p
Hey @Matt (pactflow.io / pact-js / pact-go) We have acquired a DNS for our pact-onprem http://pactflow.<mycompany>.com/ Wanted to knwo if I need to put the above value for the environment variable shown in screenshot.
m
(e.g. Okta, Azure AD etc.)
👍 1
p
This is the deployment script for deploying to PKS. It is working with demo auth but when I configured it with SAML, it still shows demo auth? Am I missing something here?
It is still looking like this with the configurations made
m
I would take a look at the boot logs of the application, ideally set to DEBUG mode. This will enable you to see what the application is getting during bootstrap. Also, is there a reason you’re still using the trial license?
p
Do you mean with the trial license we cannot enable the authentication? We are still in DEMO phase, hence using trial license for now. Also, where can I find the boot logs of THIS APPLICATION?
m
It's fine to use the trial I was just wondering
👍 1
The boot logs are wherever your kube cluster sends them
👀 1