Hello,
the traceback is pointing to an issue with the client secret. Make
sure you have configured correctly the cdb.json file, and have
included the correct secret for that specific client there. Right now,
it seems to be missing. See, the example entry here:
https://github.com/IdentityPython/SATOSA/blob/f3b250e/example/cdb.json.exam…
Cheers,
On Mon, 5 Oct 2020 at 05:21, 김용욱 <j2mity at gmail.com> wrote:
Hello
I'm having a strange error with my Satosa (oidc-to-saml) frontend
[satosa.frontends.openid_connect]: invalid client authentication at token endpoint
Traceback (most recent call last):
File
"/usr/local/lib/python3.6/site-packages/satosa/frontends/openid_connect.py",
line 362, in token_endpoint
response = self.provider.handle_token_request(urlencode(context.request), headers)
File "/usr/local/lib/python3.6/site-packages/pyop/provider.py", line 319, in
handle_token_request
token_request = self._verify_client_authentication(request_body, http_headers)
File "/usr/local/lib/python3.6/site-packages/pyop/provider.py", line 425, in
_verify_client_authentication
token_request['client_id'] = verify_client_authentication(self.clients,
token_request, http_headers.get('Authorization'))
File "/usr/local/lib/python3.6/site-packages/pyop/client_authentication.py",
line 57, in verify_client_authentication
raise InvalidClientAuthentication(client_secret)
pyop.exceptions.InvalidClientAuthentication: None
The above error repeats over and over again. I'm not sure if it's problem with
client_id registration, tokenEndpoint, or Satosa internal settings. Could you tell me how
to solve this problem?
_______________________________________________
satosa-users mailing list
satosa-users at lists.sunet.se
https://lists.sunet.se/listinfo/satosa-users
--
Ivan c00kiemon5ter Kanakarakis >:3