chore: bump charm revisions

[natalian98]

This PR:

• bumps charm revisions to prepare for 0.3 bundle release

fixes #268

[nsklikas]

LGTM but I have a couple of questionts:

• Shouldn't this include tests for the Kratos IdP?
• Also should we try updating traefik?

[natalian98]

LGTM but I have a couple of questionts:

• Shouldn't this include tests for the Kratos IdP?

I'll work on this as part of https://warthogs.atlassian.net/browse/IAM-996

• Also should we try updating traefik?

Updated, thanks

[nsklikas]

Not sure if my comment makes sense, but if we want other people to use this, we need to come up with a solution that has a stable API.

If you disagree, feel free to disregard it and maybe we can come up with a solution for this in another PR

[nsklikas]

If I deploy the bundle via:

juju deploy ./bundle-edge.yaml --trust

And the try to login (via the hydra cli client), I will get redirected to the login page:

And if then click Sign in with Security key, I will see:

But if I try to input some random email, I will get an invalid password error:

Is this expected, is it a bug we should open in the login UI or is something wrong with the kratos config?

AFAICT the error comes from this line

[natalian98]

Is this expected, is it a bug we should open in the login UI or is something wrong with the kratos config?

AFAICT the error comes from this line

It is not expected, this can be reproduced if webauthn is disabled, otherwise it displays the correct message. Perhaps we should not show the "Sign in with security key" button at all in that scenario.
I opened an issue: canonical/identity-platform-login-ui#277

[nsklikas]

If I deploy the bundle, create an admin account via juju CLI, setup the authenticator and try login via Hydra:

I will end up in the totp page:

Now if I go back (without entering the otp), I will be asked only for my password (username is cached):

If I now try to reset my password, I will be asked to input my email:

But then I will be redirected to an error page:

thought about it, we could remove the traefik update and have the oauth tools changes in a separate pr

[natalian98]

As discussed with @nsklikas, I reverted the traefik revision bump to address oauth_tools updates in a separate PR.