The environment parameter "PING_IDENTITY_ACCEPT_EULA" does not work

[sansub]

Describe the bug

The environment parameter "PING_IDENTITY_ACCEPT_EULA" does not work when using any ping docker image after 11.2.x

To Reproduce
Steps to reproduce the behavior:

1. Update docker-compose.yaml to use a new image after 11.2 eg: pingidentity/pingfederate:12.0.6-edge
2. Add the below environment parameter to the file:
   PING_IDENTITY_ACCEPT_EULA=YES
3. run docker-compose
4. See error
   ╷
   │ Error: Connection Error
   │
   │ with provider["registry.terraform.io/iwarapter/pingfederate"],
   │ on versions.tf line 11, in provider "pingfederate":
   │ 11: provider "pingfederate" {
   │
   │ Unable to connect to PingFederate: License Agreement has to be accepted to use PingFederate.

This does not happen if we use an older image eg: pingidentity/pingfederate:11.1.1-edge

The below document confims that the environment parameter is supported.

https://devops.pingidentity.com/docker-images/pingfederate/

Expected behavior

The pingfederate docker image is running and ready for further configuration.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment:

• • Docker Container: pingfederate, pingaccess

Additional Info
Add any other information about the problem here.

[henryrecker-pingidentity]

Hi @sansub , that environment variable is only used when retrieving the license initially, it is not used for accepting the license for PF with the /license/agreement endpoint. You can see it's only usage related to PingFederate here, where it will fail the container if not set to YES: https://github.com/pingidentity/pingidentity-docker-builds/blob/ac7e8f2062e83b39a0acd9d854e4b8445f885b05/pingcommon/opt/staging/hooks/17-check-license.sh#L89

The license is accepted as a part of 83-configure-admin.sh, which is run when you either have a data.json in your server profile to import, or when you have set the CREATE_INITIAL_ADMIN_USER variable to true: https://github.com/pingidentity/pingidentity-docker-builds/blob/master/pingfederate/opt/staging/hooks/81-after-start-process.sh .

It's possible that it could be an issue with the terraform provider. We aren't able to support the iwarapter/pingfederate terraform provider since it is community-made, but we do have a Ping-supported terraform provider available here: https://registry.terraform.io/providers/pingidentity/pingfederate/latest.