Skip to content
Lauri Ojansivu edited this page Oct 2, 2020 · 3 revisions

Login with OIDC OAuth2 Oracle OIM, on premise identity manager

Added with this commit.

Here is a summary of code and changes by anonymous Wekan contributors and xet7:

  • If the OAuth2 token doesn't contain the email address, Wekan raises an exception. The userinfo and servicedata were changed to avoid that.
  • In the getToken function, OIM expects a POST request that contains OAUTH2_CLIENT_ID and OAUTH2_SECRET in its header. We fixed that.
  • We also had to edit the app.js in order to put a custom "scope" value. But we think the target should be to be able to set this as an environment variable.
  • Another point concerns OAUTH2_REQUEST_PERMISSION. It must be exactly BDFUserProfile.me. xet7 hardcoded it in above commit at wekan/server/authentication.js
  • There is a problem in the code when email is null or empty. I know it might not be null but we have some situation where it is. xet7 maybe fixed it in above commit so that if email is missing, it takes that value from username. When logging into Wekan with OIDC, both username and email should be mapped to email.
  • TODO: Testing does everything work with these changes.

About settings

Other OIDC settings are similar like in this wiki OAuth2, Google, Azure etc settings. Both username and email should be mapped to email.

Snap

sudo snap set wekan oracle-oim-enabled='true'

Unset Snap:

sudo snap unset wekan oracle-oim-enabled

Docker

- ORACLE_OIM_ENABLED=true

Wekan

General

Support priorities for new features and bugfixes

  1. Commercial Support
  2. Community Support
  3. Debugging

Security

Backup

Repair

Themes

Features

Email

Logs and Stats

Migrating

Required Settings

Download

Webservers

REST API Docs

REST API issue

REST API client code

Webhooks

Case Studies

Development

Issues

Clone this wiki locally