Support for issue #200

[SofianeB]

Hi,

I didn't know exactly if it was the right place.
Can you help on this?

erlef/oidcc#200

Thank you.

Best,

Sofiane.

[marcvs]

Hi, what's up?

…

On 07/17/18 00:51, SB wrote: -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: #49

-- Marcus.

[SofianeB]

I am trying to connect our jupyterhub instance via keycloak to INDIGO IAM (https://iam-test.indigo-datacloud.eu/.well-known/openid-configuration). The redirection to the login/confirmation page works perfectly.
Unfortunately, I am getting cannot get access_token from server.

Did I miss something during configuration?

I created an account and then a client, exported the JSON file and upload it to keycloak.

[marcvs]

I guess I don't fully understand your usecase. I.e.: I'm not sure why keycloak is required here. Also could you shed light on how this is related with OIDCC (the erlang oidc lib). Cheers, Marcus.

…

On 07/17/18 01:01, SB wrote: I am trying to connect our jupyterhub instance via keycloak to INDIGO IAM (https://iam-test.indigo-datacloud.eu/.well-known/openid-configuration). The redirection to the login/confirmation page works perfectly. Unfortunately, I am getting cannot get access_token from server. Did I miss something during configuration? I created an account and then a client, exported the JSON file and upload it to keycloak. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #49 (comment)

-- Marcus.

[SofianeB]

I though that INDIGO DC IAM is related to OIDCC. Maybe I am wrong. You can close this if this is the case.

[marcvs]

Well, it's not related to OIDCC. However, if you're using the oidc-agent to obtain an AT (e.g. from IAM) and want to use that to access jupyter notebooks (which I find an interesting case) you're most welcome! M.

…

On 07/17/18 08:28, SB wrote: I though that INDIGO DC IAM is related to OIDCC. Maybe I am wrong. You can close this if this is the case. -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #49 (comment)

-- Marcus.

[SofianeB]

Thanks @marcvs I don't know what just happened, but the integration is working!