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

Allow swagger to use overridden CSRF settings and read the CSRF cookie #660

Conversation

terencehonles
Copy link
Contributor

No description provided.

@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch 3 times, most recently from c098a02 to 0d7c8cf Compare October 26, 2020 20:07
Copy link
Contributor Author

@terencehonles terencehonles left a comment

Choose a reason for hiding this comment

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

@axnsan12 this should also be a pretty easy PR to review, I bumped it to run the CI tests again.

@@ -33,6 +33,8 @@
'DEFAULT_API_URL': None,

'USE_SESSION_AUTH': True,
'CSRF_COOKIE_NAME': settings.CSRF_COOKIE_NAME,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'm pretty sure these will be available, but I can change this to gettar like below if that is preferred.

@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 0d7c8cf to 17aecc3 Compare November 5, 2020 03:30
@terencehonles
Copy link
Contributor Author

@johnthagen it looks like you might also have commit access to the repo? Do you mind reviewing? I just update the changes and kicked off the CI.

@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 17aecc3 to 2697326 Compare September 24, 2021 01:42
@terencehonles
Copy link
Contributor Author

@axnsan12 any chance I can get a review on this / have this merged?

@JoelLefkowitz
Copy link
Collaborator

I’ll review this now

@JoelLefkowitz JoelLefkowitz self-assigned this Sep 24, 2021
@JoelLefkowitz JoelLefkowitz changed the base branch from master to 1.20.x September 24, 2021 06:50
@JoelLefkowitz JoelLefkowitz changed the base branch from 1.20.x to 1.21.x July 17, 2022 17:17
@JoelLefkowitz JoelLefkowitz added 1.21.x Release target in 1.21.x enhancement Enhancement proposal 1.22.x Release target in 1.22.x and removed 1.21.x Release target in 1.21.x labels Jul 17, 2022
@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 91e871a to 3c14a2c Compare August 11, 2022 10:13
@terencehonles
Copy link
Contributor Author

terencehonles commented Aug 11, 2022

updated this to the latest version of 1.21.x

@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 3c14a2c to 06debd7 Compare August 11, 2022 10:25
@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 06debd7 to a2be3e5 Compare November 1, 2022 09:39
@terencehonles
Copy link
Contributor Author

updated this to the latest version of 1.21.x

@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from a2be3e5 to 271aa3d Compare March 2, 2023 16:11
@terencehonles terencehonles force-pushed the allow-swagger-to-use-custom-csrf-settings branch from 271aa3d to fc9a9df Compare July 6, 2023 18:13
@JoelLefkowitz JoelLefkowitz merged commit 5f889de into axnsan12:1.21.x Jul 21, 2023
5 checks passed
@JoelLefkowitz
Copy link
Collaborator

@terencehonles thank you!

@terencehonles terencehonles deleted the allow-swagger-to-use-custom-csrf-settings branch July 24, 2023 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.22.x Release target in 1.22.x enhancement Enhancement proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants