...
| Panel | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| |||||||||
|
Activity overview
| Panel | ||
|---|---|---|
| ||
This activity attempts to export the command line tool oidc-agent, which exists for Linux and Mac, to Windows. | ||
| Panel | ||
| ||
The aim of this activity is to provide a working version of the oidc-agent for Windows. |
Activity Details
| ||
oidc-agent is a command line set of tools that enables the users to manage and obtain (mostly) OIDC tokens on command line. It follows the design of the ssh-agent and, as such, it can be easily integrated in the user's flow. However, current version only covers Linux and MacOS users. This activity would port the oidc-agent to Windows OS. The expected impact is potentially large, since users from many communities that may use this tool (such as HPC, or any community that need constant access to computing and storage resources as part of their work) typically rely on Windows as their main operating system. |
| Panel | ||
|---|---|---|
| ||
The aim of this activity is to provide a working version of the oidc-agent for Windows. |
Activity Details
| Panel | ||
|---|---|---|
| ||
This activity investigates activity would investigate the best approach to porting the oidc-agent. Two potential approaches are currently identified, but naturally, they can be changed or ignored.: First focus on using Windows Subsystem for Linux (WSL) and then installing oidc-agent as an application inside Linux. This approach may have a downside of requiring users to only rely on command-line (which may not be comfortable for Windows users) and the potential issue of communicating with a browser (that is required in order for users to obtain a token). Second approach could be by extending PuTTY. PuTTY is a SSH and TTY client for Windows and Linux that comes with a GUI. The idea is to integrate oidc-agent functionalities in PuTTY. The advantage is the ease-of-use and easier communication with Windows OS browsers. |
| Panel | ||
|---|---|---|
| ||
This activity provides an innovative solution towards a clear need in the research communities to use modern web based technologies for access to non-webbased resources. A windows version of this solution has the potential to much broaden the usability. However, at this point it seems mostly KIT related services are leveraging technology. Therefore, as part of the activity the Incubator will also engage with at least one independent service operator to collaborate in testing this technology. |
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
| ||
The activity does not affect data protection or privacy. |
...
| Panel | ||
|---|---|---|
| ||
|
| Panel | ||
|---|---|---|
| ||
KIT will keep maintaining the software after the end of the Incubator. The source code was submitted to the upstream repository and is publicly available to the community. |
Activity Results
| Panel | ||
|---|---|---|
| ||
|
Meetings
Date | Activity | Owner | Minutes | |
|---|---|---|---|---|
01.06.21 | Niels van Dijk | |||
| 21.09.21 | Final demo | Niels van Dijk | January 1, 2017 | Kickoff meeting |
Documents
Attachments