Guardian custom header verification instead of Authorization

I have two tokens coming to my Endpoint method. one with inside the key of Authorization and another one inside App-token but couldn’t find any docs/support or anything to workaround this. what is the possible workaround to validate both tokens

I see this option
plug(Guardian.Plug.VerifyHeader, claims: %{"typ" => "access"}, realm: "Bearer") of realm but not of custom header name

Hi, a bit late here but I think the best way to go about doing this is to create two guardian instances, two pipelines and then pass your connection through both those authentication pipelines. Something like this:

scope "/", ExampleWeb do
    pipe_through: [:auth, :app_token, :api]
    #do something here.