66 improve the restaction flow to use parametrized restactions

[FrancescoL96]

The RESTAction implementation in Authn has been improved in this PR but it introduced a breaking change for those OAuthConfig and OIDCConfig that make use of RESTActions: previously, Authn would make a copy of the Endpoint used by the RESTAction to add and use the just acquired bearer token. Then, it would also create a copy of the RESTAction to use the newly created Endpoint to access the authenticated APIs (to gather the extra user details). Finally, it deleted both the Endpoint and the RESTAction.

This process has been made redundant by the introduction of the parametrized RESTAction, which allows to passing the RESTAction additional parameters. In this breaking change, we are passing the bearer token directly in the field .token, which will be used in the Authorization Header.

The change will require adding the authorization header manually in existing RESTActions for OAuth2 and OIDC when upgrading Authn:

    headers:
    - "${ \"Authorization: Bearer \" + .token }"

To see the complete examples diffs for the existing RESTActions for both OAuth2 and OIDC: diff.

The breaking change is scheduled for Authn version 0.22.0.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 47 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
internal/helpers/restaction/resolver.go	0.00%	29 Missing ⚠️
internal/routes/auth/oauth/login.go	0.00%	9 Missing ⚠️
internal/routes/auth/oidc/login.go	0.00%	9 Missing ⚠️

📢 Thoughts on this report? Let us know!