Configure Oauth2 Dynamic Registration for Webapp running on Apache2
Budget: $10 – $30 USD
I have an Apache 2-based web application that needs to use Google as its OAuth2 provider. I need a clean, reproducible configuration that lets users sign in with their Google account, then redirects them back to the app with the correct tokens.
Here is what I’m looking for:
• Guidance inside Google Cloud Console to create the project, consent screen, OAuth2 credentials, and authorised redirect URIs.
• The exact Apache configuration (VirtualHost entries, required modules, environment variables, and any RewriteRule or ProxyPass directives) so a fresh server can be brought up and immediately support Google sign-in.
• A short README or commented config blocks explaining where to drop client_id, client_secret, scopes, and token endpoints so I can maintain it later.
I’ll provide SSH access to a test server and the current vhost file. Once I can log in through Google on that test instance and the flow survives an Apache restart, the job is complete.
Here is what I’m looking for:
• Guidance inside Google Cloud Console to create the project, consent screen, OAuth2 credentials, and authorised redirect URIs.
• The exact Apache configuration (VirtualHost entries, required modules, environment variables, and any RewriteRule or ProxyPass directives) so a fresh server can be brought up and immediately support Google sign-in.
• A short README or commented config blocks explaining where to drop client_id, client_secret, scopes, and token endpoints so I can maintain it later.
I’ll provide SSH access to a test server and the current vhost file. Once I can log in through Google on that test instance and the flow survives an Apache restart, the job is complete.
Related categories:
Linux
Cloud Computing
Apache
MySQL
OAuth
Web Development
API
Backend Development
API Integration