Document error redirect to identity provider #96
Assignees
Milestone
Comments
|
if an error occurs, the idp url should contain a uri query param called this happens when, according to spec, hydra is not allowed to redirect back to the client callback when an error occurs. let me know if the error param is not available and reopen this issue. |
|
However, this should be documented |
aeneasr
changed the title
aeneasr
pushed a commit
that referenced
this issue
Jul 25, 2016
aeneasr
pushed a commit
that referenced
this issue
Aug 9, 2016
* warden: rename `assertion` to `token` - closes #158 * config: do not log database credentials - closes #147 * oauth2: upgrade fosite - close #160 * config: do not store database config in hydra config - closes #164 * oauth2: id_token at_hash / c_hash is null - closes #129 * jwk: improve error message of wrong system secrect - closes #104 * readme: improve images, add benchmarks - closes #161 * cmd: improve connect dialogue - closes #170 * cmd: fix --dry option - closes #157 * firewall: document warden interface sdk * readme: link openid connect and oauth2 introduction * cmd: introduce FORCE_ROOT_CLIENT_CREDENTIALS env var - closes #140 * readme: document error redirect to identity provider - closes #96 * internal: fosite store must be consistent to avoid errors - closes #176 * client: add GetConcreteClient to http manager * cmd: host process now logs basic information on all http requests - closes #178 * all: add memory profiling - closes #179 * warden: resolve nil pointer issue - closes #181 * cmd: clean up env to struct mapping, add more controls * cmd: bcrypt cost should be configurable - closes #184 * cmd: token lifespans should be configurable - closes #183 * cmd: resolve issues with envirnoment config - closes #182 * cmd: implement tls termination capability - closes #177 * cmd: resolve issues with redirect logic and TLS * oauth2: implement default oauth2 consent endpoint - closes #185 * warden - closes #188 * oauth2: id token claims should be set by using id_token - closes #188 * oauth2: oauth2 implicit flow should allow custom protocols - closes #180 * oauth2: core scope should not be mandatory - closes #189 * warden: warden sdk should not make distinction between token and request - closes #190 * warden: rename authorized / allowed endpoints to something more meaningful - closes #162 * ci: improve travis config
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I think I found a small bug in consent handling by Hydra when integrating with a IdP.
When I run
hydra token user --skip-tls-verifyI get a URL.The first time I visit it's OK and I get:
The second time I visit I get an error and that's ok.
However the IdP gets called anyway and this is probably bad.
The text was updated successfully, but these errors were encountered: