Martin Claus
Martin Claus
It would be nice to mention in the documentation that the path to the template must be an absolute path. Especially since there are some [examples out there](https://github.com/jupyterhub/jupyterhub/issues/1385#issuecomment-465801218) which use...
The actual URL of the index.yaml is something like https://artifactory.mydomain.com:443/artifactory/api/helm/helm-charts-test/index.yaml, which is different from the URL you have used. You can check this by downloading the index.yaml through the artifactory...
Same issue here. The plugin worked correctly for some month. Since today, I get the same error. `mono-complete` is installed on my box (ubuntu 16.04.2) and clearing the cache did...
Hi @jlanza, support for LTI 1.3 is currently added (#134) and will be part of the next release. But you are correct, the documentation and README really require some attention....
Hi @jlanza! LTI 1.3 support (#134) is merged into the main branch and I have updated the LTI 1.3 section of the README. I hope the configuration of the LTI13Authenticator...
Hi @hugokoopmans, you were quicker than me :smile:. Indeed, ltiauthenticator cannot run alongside another authenticator as mentioned in the [README](https://github.com/jupyterhub/ltiauthenticator#readme). Though, it could be mentioned in the docs too. Actually,...
@kathoef Thanks for your suggestion. Unfortunately, the linked repository contains "only" a PHP library to build LTI conformant tools. It is not the system that serves https://saltire.lti.app. While this page...
> My setup is almost functional, but I am struggling with docker DNS issues. That is solved.
It seems that the [LTI 1.3 library](https://github.com/oat-sa/lib-lti1p3-core) on which the devkit is build isn't correctly implementing the LTI 1.3 specifications, or more precisely, the OICD Connect specifications. Issues (https://github.com/oat-sa/lib-lti1p3-core/issues/154, https://github.com/oat-sa/lib-lti1p3-core/issues/160)...
> I noticed that a `c.LTI13Authenticator.jwks_endpoint` configuration setting is used in the docs but this PR has a `c.LTI13Authenticator.endpoint ` setting ... are those both valid? @danielmcquillen This PR is...