Skip to content

Return error when SAML year is invalid#11766

Merged
mitchellhenke merged 1 commit intomainfrom
mitchellhenke/do-not-raise-exception-on-missing-year
Jan 21, 2025
Merged

Return error when SAML year is invalid#11766
mitchellhenke merged 1 commit intomainfrom
mitchellhenke/do-not-raise-exception-on-missing-year

Conversation

@mitchellhenke
Copy link
Contributor

🛠 Summary of changes

We currently raise an unhandled exception in some cases when receiving a request for a SAML year that is not currently configured. This PR stores the SAML years from AppArtifacts in a constant and adds a year check to the SAML controller that returns an error if the year is not available.

@mitchellhenke mitchellhenke force-pushed the mitchellhenke/do-not-raise-exception-on-missing-year branch from bca38bc to 04f93ba Compare January 17, 2025 17:02
changelog: Bug Fixes, SAML, Return error when SAML year is invalid
@mitchellhenke mitchellhenke force-pushed the mitchellhenke/do-not-raise-exception-on-missing-year branch from 04f93ba to 9007544 Compare January 17, 2025 17:19
Copy link
Contributor

@Sgtpluck Sgtpluck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@mitchellhenke mitchellhenke merged commit d2a4643 into main Jan 21, 2025
@mitchellhenke mitchellhenke deleted the mitchellhenke/do-not-raise-exception-on-missing-year branch January 21, 2025 16:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants