Follow redirects while testing AuthnRequests

[italia]

Follow redirects while testing AuthnRequests

[glatrofa]

@nicolabeghin I used a keycloak oidc client url, like this one: http://localhost:8080/realms/spid/protocol/openid-connect/auth?client_id=account&scope=openid&response_type=code&redirect_uri=http://localhost:8080/realms/spid/account&state=12345&kc_idp_hint=spid-validator-demo

[peppelinux]

Yes, an authn plugin with follow_redirect as parameter in the requests, we'll check together. I'll reach you on slack

[nicolabeghin]

Hi @lscorcia @peppelinux I'm starting to dig possible usage of spid-sp-test with Keycloak and the on-going SPID plugin https://github.com/italia/spid-keycloak-provider - any hint/progress on the above that I should be aware of? just to avoid having to reinvent the wheel, thanks!

[peppelinux]

Spid-sp-tests uses plugings for proxies, you can read the plugin of satosa, It uses http-post

You can change It to follow http redirect

[glatrofa]

Hi @lscorcia, have you managed to solve this redirect issue and correctly test the authn request generated by keycloak?

[glatrofa]

The request starts changing "allow_redirects": False to "allow_redirects": True at line 146 from 'spid-sp-test/src/spid-sp-test/authn_request.py' and building locally the docker image.
Only the test n. 11 will fail due to the different path to which the request is sent.

[nicolabeghin]

@glatrofa out of curiosity: how did you build the --authn-url to be passed to spid_sp_test? (if manually) thanks!