Deploy pingctl
This enables us to create the necessary secrets needed to enable Ping Licenses for the deployment.
sudo mv /home/nirving/pingctl /usr/local/bin/.
The following enables the creation of the secrets
Add Ping DevOps
help repo update
Create an updated Ingress file
envs:
PING_IDENTITY_ACCEPT_EULA: “YES”
ingress:
enabled: true
annotations:
nginx.ingress.kubernetes.io/backend-protocol: “HTTPS”
cert-manager.io/cluster-issuer: vault-issuer
spec:
ingressClassName: nginx
pingauthorize:
ingress:
hosts:
– host: pingauthorize.pingauthorize.internal.darkedges.com.au
paths:
– path: /
pathType: Prefix
backend:
serviceName: https
tls:
– secretName: pingauthorize
hosts:
– pingauthorize.pingauthorize.internal.darkedges.com.au
pingauthorizepap:
ingress:
hosts:
– host: pingauthorizepap.pingauthorize.internal.darkedges.com.au
paths:
– path: /
pathType: Prefix
backend:
serviceName: https
tls:
– secretName: pingauthorizepap
hosts:
– pingauthorizepap.pingauthorize.internal.darkedges.com.au
pingdataconsole:
ingress:
hosts:
– host: pingdataconsole.pingauthorize.internal.darkedges.com.au
paths:
– path: /
pathType: Prefix
backend:
serviceName: https
tls:
– secretName: pingdataconsole
hosts:
– pingdataconsole.pingauthorize.internal.darkedges.com.au
pingdirectory:
ingress:
hosts:
– host: pingdirectory.pingauthorize.internal.darkedges.com.au
paths:
– path: /
pathType: Prefix
backend:
serviceName: https
tls:
– secretName: pingdirectory
hosts:
– pingdirectory.pingauthorize.internal.darkedges.com.au
Deploy Ping Authorize
helm upgrade –install pingauthorize pingidentity/ping-devops –create-namespace –namespace ping -f https://raw.githubusercontent.com/pingidentity/pingidentity-devops-getting-started/master/30-helm/pingauthorize-pingdirectory.yaml -f ingress.yaml
Console
Directory
https://pingdataconsole.pingauthorize.internal.darkedges.com/
Server
Username
Password
pingauthorize-pingdirectory
administrator
2FederateM0re
Policy Editor
https://pingauthorizepap.pingauthorize.internal.darkedges.com/login
username
password
admin
password123