Adding a SAML Validation error when there is no registered certs#11609
Merged
Adding a SAML Validation error when there is no registered certs#11609
Conversation
… better error for a testing scenario
Sgtpluck
commented
Dec 6, 2024
| errors.messages.invalid_sms_number: El número de teléfono ingresado no admite mensajes de texto. Intente la opción de llamada telefónica. | ||
| errors.messages.invalid_voice_number: Número de teléfono no válido. Verifique haber ingresado el código de país o de área correcto. | ||
| errors.messages.missing_field: Llene este campo. | ||
| errors.messages.no_cert_registered: No podemos detectar un certificado en su solicitud. |
Contributor
Author
There was a problem hiding this comment.
the non-english versions of this error are just the blank_cert_element_req errors. since these will not be seen by users in prod, i think this should be fine (the errors won't make much sense to users in either case) -- but i am asking the UX team if they feel strongly about this.
Contributor
Author
There was a problem hiding this comment.
they gave me the all-clear!
mitchellhenke
approved these changes
Dec 6, 2024
Contributor
|
I'm satisfied that this checks for the condition we were concerned about. As someone who's not too up on IDP, where could I expect to see this error after it happens? |
Contributor
Author
|
@h-m-m the error happens in the same error page where you'd see all our current SAML integration errors. if you'd like to test it out:
cleanup, in the rails console: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎫 Ticket
Add "No Certs" Error
🛠 Summary of changes
Slack conversation here
Ursula bug ticket here
We have validations in the identity-idp-config repo to prevent partners from deploying non-pkce integrations without certificates to prod. However, we do not have those validations in the Partner Portal (because sometimes a partner doesn't have all the finalized details before creating an integration.)
This means that a partner could attempt to test an integration without a certificate, which currently blows up when we attempt to encrypt the response. This change adds a specific validation to ensure that a requesting service provider has registered a certificate, and if it has not, it returns an error.