Given that your key has expired.
$ gpg --list-keys
$ gpg --edit-key KEYID
Use the expire command to set a new expire date:
| # .bash_profile is executed for login shells, | |
| # .bashrc is executed for interactive non-login shells. | |
| # We want the same behaviour for both, so we source .bashrc from .bash_profile. | |
| # Also, when .bash_profile exists, bash ignores .profile, so we have to source | |
| # it explicitly. | |
| if [ -f "$HOME/.profile" ]; then | |
| . "$HOME/.profile" | |
| fi |
| # -*- coding: utf-8 -*- | |
| import requests | |
| from io import BytesIO, SEEK_SET, SEEK_END | |
| class ResponseStream(object): | |
| def __init__(self, request_iterator): | |
| self._bytes = BytesIO() | |
| self._iterator = request_iterator |
| #!groovy | |
| // imports | |
| import jenkins.model.Jenkins | |
| import jenkins.model.JenkinsLocationConfiguration | |
| // parameters | |
| def jenkinsParameters = [ | |
| email: 'Jenkins Admin <admin@jenkins.com>', | |
| url: 'https://ci.jenkins.com:8083/' |
This LTI dynamic registration implementation follows this guide: https://moodlelti.theedtech.dev/dynreg/
It allows you to create a one-off registration link, which you can use to register your Django application at a tool consumer, using the pylti1p3 package.
If you use this code, please refer to the guide / spec to see which fields to include in the JSONs that are being exchanged with the consumer. This implementation has only been tested with Moodle.