mirror of
https://github.com/lukaszraczylo/traefikoidc.git
synced 2026-06-05 22:44:17 +00:00
lukaszraczylo
ae59a5e88a
* Add ability to disable replay protection. - This is useful for runs with multiple traefik replicas to avoid false positives and tokens re-creation. * Enhance the CI/CD pipelines * Increase test coverage. * Update vendored dependencies. * Update behaviour on forceHTTPS as per issue #82
2.8 KiB
2.8 KiB
Description
Type of Change
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation update
- Performance improvement
- Code refactoring
- Security fix
- Provider-specific fix/enhancement
Related Issues
Fixes # Related to #
Changes Made
Provider Impact
- Azure AD
- Auth0
- Okta
- Keycloak
- AWS Cognito
- GitLab
- GitHub
- Generic OIDC
- All providers
Testing Performed
- Unit tests pass locally
- Integration tests pass locally
- Race detector shows no issues
- Memory leak tests pass
- Manual testing performed
Test Configuration
Provider tested: Go version: Traefik version:
Security Considerations
- This PR does not introduce security vulnerabilities
- Security scanning has been performed
- Credentials/secrets are properly handled
- Input validation is implemented
Performance Impact
- No performance impact expected
- Performance improved (describe how)
- Performance may be affected (describe why and mitigation)
Breaking Changes
Breaking changes:
Migration guide:
Checklist
- My code follows the project's code style
- I have performed a self-review of my code
- I have commented my code, particularly in hard-to-understand areas
- I have made corresponding changes to the documentation
- My changes generate no new warnings
- I have added tests that prove my fix is effective or that my feature works
- New and existing unit tests pass locally with my changes
- Any dependent changes have been merged and published
Additional Context
Screenshots (if applicable)
For Reviewers:
Please verify:
- Code quality and style
- Test coverage is adequate
- Security implications reviewed
- Documentation is updated
- No performance regressions