Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support new provider, retry and fail_expired_id properties in verify_policy configuration. #805

Closed
mjspi opened this issue May 4, 2024 · 0 comments · Fixed by #888
Closed
Assignees
Labels
service/verify PingOne Verify size/small Small change (e.g. adding a small number of parameters to an existing resource/datasource schema) type/enhancement New feature or request
Milestone

Comments

@mjspi
Copy link
Contributor

mjspi commented May 4, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Description

New properties in the liveness and government_id configurations in pingone_verify_policy.

The liveness configuration object has a new property retry_attempts.

  • The value is an integer.
  • The value is optional
  • The minimum value is 0. The maximum value is 3.

The government_id configuration object has 4 new properties: fail_expired_id, retry_attempts, provider_auto and provider_manual.

  • The retry_attempts requirements are identical to the retry.attempts property in the liveness configuration option.
  • The provider_auto property is a string with the allowable values MITEK (default) or VERIFF. The value is optional.
  • The provider_manual property is a string with the allowable value MITEK. The value is optional.
  • The fail_expired_id property is a boolean. The value is optional.

New or Affected Resource(s)

pingone_verify_policy

Potential Terraform Configuration

# Copy-paste your PingOne related Terraform configurations here - for large Terraform configs,
# please use a service like Dropbox and share a link to the ZIP file. For
# security, you can also encrypt the files using our GPG public key.

# Remember to replace any account/customer sensitive information in the configuration before submitting the issue
resource "pingone_verify_policy" "sample_policy" {
  environment_id = data.pingone_environment.general_test.id
  name           = "sample policy"
  description    = "Description for sample policy"

  government_id = {
    verify = "REQUIRED"

    # new properties
    fail_expired_id = true
    provider_auto = "VERIFF"
    provider_manual = "MITEK"
    retry_attempts = 2
  }

  liveness = {
    verify = "OPTIONAL"

    # new properties
    retry_attempts = 3
  }
}

References

API References:

@mjspi mjspi added type/enhancement New feature or request service/verify PingOne Verify status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK size/small Small change (e.g. adding a small number of parameters to an existing resource/datasource schema) labels May 4, 2024
@mjspi mjspi changed the title Support provider and retry options in verify_policy configuration. Support provider, retry and failExpiredId options in verify_policy configuration. Jun 27, 2024
@mjspi mjspi changed the title Support provider, retry and failExpiredId options in verify_policy configuration. Support provider, retry and fail_expired_id options in verify_policy configuration. Jun 27, 2024
@mjspi mjspi changed the title Support provider, retry and fail_expired_id options in verify_policy configuration. Support new provider, retry and fail_expired_id properties in verify_policy configuration. Jul 6, 2024
@mjspi mjspi self-assigned this Jul 6, 2024
@patrickcping patrickcping added this to the v1.1.0 milestone Aug 2, 2024
@patrickcping patrickcping removed the status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK label Aug 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
service/verify PingOne Verify size/small Small change (e.g. adding a small number of parameters to an existing resource/datasource schema) type/enhancement New feature or request
Projects
None yet
2 participants