Create tests to cover full auth flow

[alexeykazakov]

Currently our tests cover only the first part of the flow when we call /api/login/authorize to create a state and redirect to KC. We need to cover the second part when after successful authentication KC redirects back to /api/login/authorize and passing the state from the first call.

[sbose78]

Hi

We need to cover the second part when after successful authentication KC redirects back to /api/login/authorize and passing the state from the first call.

/api/authorize/login is called using state and code .
We can't really have a positive test for code because it is generated after a successful user interaction.

We already have

• test for incorrect state.
• test for correct state & incorrect code.

So no matter what, config.Exchange(ctx, code) would always return an error.

I don't see what tests more we can add for this second step, do you have something different in mind, @alexeykazakov ?

[alexeykazakov]

This is a standard (statefull) oauth workflow. What we could do here is to simulate our Keycloak and browser:

1. Call Perform() As a response we will get a redirect URL with the state.
2. Extract this state and call Perform() again passing all needed params simulating a callback/redirect from Keycloak/browser.

[alexeykazakov]

Moved to fabric8-services/fabric8-auth#34
Closing.