Any idea why I’m getting this when trying to issue a POST request? ActionController::RoutingError (No route matches [POST] “/admin/users/sync_sso”) Thanks!

You aren’t passing api_username and api_key. You need those as query params. You can check our howto in the topic here: Sync DiscourseConnect user data with the sync_sso route

sso.buildLoginString is doing that. discourse_sso.prototype.buildLoginString = function(params) { if(!("external_id" in params)) { throw new Exception("Missing required parameter 'external_id'"); } if(!("nonce" in params)) { throw new Exception("Missing required parameter 'nonce'"); } if(!…

[immagine] Nopsled: sso.buildLoginString is doing that. Where? I don’t see api_username and api_key anywhere.

Right. I was adding in as form data before. Here is the updated. Still getting the Route Not Found error in the rails logs though. const userparams = { nonce, api_username: someusername, api_key: somekey, external_id: user._id.toString(), email:…

Code that produces the bottom query: const userparams = { external_id: user._id.toString(), email: user.email, username: user.username.replace(/\s/g, ''), }; const payload = new Buffer(querystring.stringify(userparams), 'utf8').toString('base64'); const hmac = crypto.c…

Any thoughts on the above? Does that look right?

You’re delivering the wrong Content-Type. Try providing the object directly as the body to fetch, without querystring.stringify. also, hang on a sec, i’m going to let you finish, but URLSearchParams is the best browser api of 2016

[immagine] Falco: You need those as query params. [immagine] Nopsled: Here’s the query that gets generated and passed as the body on the POST route: sso=somelongSSOgenerated.&sig=somelongsignature&api_username=someusername&api_key=someAPIKey The api_* parameters need to be in the quer…

Ah understood. So the api_username and api_key in the query parameters and the rest in the post body.

[immagine] supermathie: The api_* parameters need to be in the query parameters, not the POST body. [immagine] Nopsled: So the api_username and api_key in the query parameters and the rest in the post body. They can also be in the body All my Postman requests have them in the body: […

/admin/users/sync_sso ... Percorso non trovato

Supporto SSO

shahidmir (shahid) 24 Maggio 2018, 4:41pm 22

regenerating the system api key has seem to have done the trick for some reason, though i dont know why. So I can now use the SSO_SYNC via postman.

4 Mi Piace

SSO_SYNC not found

Argomento		Risposte	Visualizzazioni
SSO_SYNC not found SSO rest-api	9	1073	Maggio 20, 2022
SSO_SYNC not working SSO	6	2566	Maggio 10, 2018
Help me troubleshoot my Discourse SSO Support	11	2655	Luglio 24, 2020
/admin/users/sync_sso 403 Forbidden SSO	1	1443	Marzo 12, 2019
Sync_sso post suddenly resulting in 404 not found after succesfully adding a portion of the users Support	1	742	Agosto 16, 2021

/admin/users/sync_sso ... Percorso non trovato

Argomenti correlati