Skip to content

Custom oAuth2 stopped working #4677

Closed
Closed
@markuswinkler

Description

@markuswinkler

Issue Description

I have a custom oAuth2 configuration for linkedIn that worked fine until recently.
The oAuth2 redirect url doesn't get handled anymore.
Anyone else ran into that problem?

Expected Results

redirect to the custom oAuth2 handler

Actual Outcome

displays "Cannot get /oauth/linkedin"

Environment Setup

config file:

const api = new ParseServer({
	databaseURI: databaseUri,
	databaseOptions: {
		poolSize: 10,
		reconnectTries: 15,
		socketOptions: {keepAlive: 1, connectTimeoutMS: 30000},
		auto_reconnect: true
	},
	cloud: process.env.CLOUD_CODE_MAIN || __dirname + "/cloud/main.js",
	appId: process.env.APP_ID,
	masterKey: process.env.MASTER_KEY,
	serverURL: process.env.SERVER_URL,
	enableAnonymousUsers: false,
	allowClientClassCreation: false,
	facebookAppIds: process.env.PARSE_SERVER_FACEBOOK_APP_IDS,
	auth: {
		facebook: {
			appIds: [process.env.PARSE_SERVER_FACEBOOK_APP_IDS ]
		},
		linkedin_crypt: {
			module: "../../../../cloud/linkedin_encrypt.js"
		}
	},
	push: {
		adapter: oneSignalPushAdapter
	}
});
  • Server
    • parse-server version : 2.7.4
    • Operating System: AWS Linux

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions