SSO_SYNC not found

Support SSO

AI-generated summary

SSO_SYNC not found

The discussion revolves around an issue with the /admin/users/sso_sync endpoint. lin_turing initially reports receiving an HTML page as a response from Postman and later discovers that the /admin/users/sync_sso route is missing.

JammyDodger points to a similar issue discussed in another topic, while Falco suggests trying API key and API username as headers, citing a change in authentication support since April 6th, 2020.

lin_turing finds Falco’s suggestion helpful, but the issue persists. blake suggests regenerating the system API key, which has worked for others in the past. However, this doesn’t resolve the issue for lin_turing.

The problem is eventually identified by LeBlanc as sending the wrong body type and Content-Type. The solution involves using multipart/form-data as the Content-Type and sending the SSO and signature parameters in the HTTP body with raw text.

1

I need some assistance with the /admin/users/sso_sync end point.
postman is returning a HTML page as response

image
image1780Ă—1182 204 KB

Can someone advise where Im going wrong.

2

/admin/users/sync_sso calls a missing route

image
image1790Ă—529 209 KB

3

can anyone help me? :sob: :sob: :sob:

4

There’s some discussion on a similar issue in this topic /admin/users/sync_sso ... Route not found, if that’s any help to you?

5

Can you try sending api_key and api_username as headers per

6

thank you ~ :smiling_face_with_three_hearts: :smiling_face_with_three_hearts:,this is very helpful for me

7

image
image1920Ă—650 63.5 KB

image
image1920Ă—622 59.6 KB

Started POST "/admin/users/sync_sso" for ip address at 2022-04-13 08:13:14 +0000
ActionController::RoutingError (No route matches [POST] "/admin/users/sync_sso")
config/initializers/100-quiet_logger.rb:23:in `call'
config/initializers/100-silence_logger.rb:31:in `call'
8

Does regenerating the system api key help?

9

no help, when i request is local, with not error, but when i request server, will go wrong

10

the problem was sending the wrong body type and Content-Type, so the sig/sso params couldn’t be parsed out. I can give you an example . use Content-Type with multipart/form-data; and use http Body with raw text (sso=$sso&sig=$sig).