Hans

Hi @nbw. I have been reading about this lately, and found this documentation from Auth0 https://auth0.com/docs/secure/attack-protection/state-parameters It seems to be valid usecase to use the state, but you should rather...

Thanks for the bug report, if you feel like it feel free to submit a PR with the fix

Hi @neilberkman & @rlb3 Sorry for the delay on this. I have tried to investigate this, the only reason I can find for this is if the full callback phase...

@doomspork I think all those a valid reasons to fail, I can just not wrap my head around why we would both end up with a `ueberauth_failure` and a `ueberauth_auth`...

Loosely related to #125

Do you mind opening a pr for this?

I can confirm that setting the path to the executable works in this case

Hi @geofflane. Thanks for the bug report. As I read the code, if you omit the secret_key from your config at compile time, Guardian should correctly fetch it from the...

> ``` > # config/config.exs > config :photon, PhotonPerm.Guardian, > issuer: "PFF.Photon" > ``` > > with > > ``` > # config/runtime.exs > config :photon, PhotonPerm.Guardian, > ttl: {14,...

I think we should be able to the compile_only only for the permission key of the environment, and then consider that to be the only compile time var atm.