Hi Guys, Need your super powers to help point me in the right direction. I am running a version of kratos with both oidc and password flow enabled kratos config:

selfservice:
  methods:
    password:
      enabled: true
    oidc:
      enabled: true

Hi @User That is odd, it is supposed to give you all nodes for identifier, password and oidc. Which version of Kratos are you using? Do the password nodes return when disabling

oidc

?

Thanks Alano, so as a work around I ended up making a back channel request to /self-service/login/browser with accept application/json and it returns the metadata correctly

Hi @User this sounds like a bug. Are you using the SDKs on your frontend?

We have written a server side web app in micronaut … we make calls to kratos on a back channel, initially the flow was send the browser down the /self-service/login/browser path … it would then redirect to redirect back to us setting a csrf cookie and providing a login challenge, we then took that cookie and flow Id and made a back channel request to /self-service/login/flow?id=flowid with cookie set as a header. In response we'd get the login form metadata which we parse and build a server side rendered form. The form is wired up with csrf_token, actionUrl and on posting a submit to it … it will do its thing. This was working in version 0.8.2 of kratos although moving to 0.9.0 caused kratos to only return the fields for oidc form instead as a result of 2nd call. So we moved our initial call to back channel as opposed to sending our browser through it and now we get the correct fields to present in the login form