Skip to content

Fix: Exposed GitHub OAuth Credentials and Hardcoded Secret Key #176

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Fix: Exposed GitHub OAuth Credentials and Hardcoded Secret Key #176

wants to merge 2 commits into from

Conversation

@Shakti13-sys
Copy link

@Shakti13-sys Shakti13-sys commented Jul 29, 2025 •
edited
Loading

  • Resolved Issue Secret Key is Hardcoded in settings.py #172: Removed hardcoded SECRET_KEY from settings.py and loaded it from environment variables.
  • Resolved Issue Exposed GitHub OAuth Credentials #173: Removed hardcoded GitHub OAuth credentials and switched to using environment variables.
  • Ensured .env is listed in .gitignore to prevent secret exposure.
  • Improved security of Django project by following best practices.

Fixes: #172 #173

@Shakti13-sys Shakti13-sys changed the title [Security Fix] Move SECRET_KEY to Environment Variable Fix: Exposed GitHub OAuth Credentials and Hardcoded Secret Key Jul 29, 2025
@Shakti13-sys
Copy link
Author

Shakti13-sys commented Aug 8, 2025

Hi @ygowthamr , it’s been a while since I submitted this PR. Could you please review it and add the appropriate level labels? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Secret Key is Hardcoded in settings.py

1 participant

@Shakti13-sys