* website: Bump prettier from 3.3.3 to 3.4.1 in /website Bumps [prettier](https://github.com/prettier/prettier) from 3.3.3 to 3.4.1. - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](https://github.com/prettier/prettier/compare/3.3.3...3.4.1) --- updated-dependencies: - dependency-name: prettier dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> * update formatting Signed-off-by: Jens Langhammer <jens@goauthentik.io> * sigh Signed-off-by: Jens Langhammer <jens@goauthentik.io> * disable flaky test Signed-off-by: Jens Langhammer <jens@goauthentik.io> --------- Signed-off-by: dependabot[bot] <support@github.com> Signed-off-by: Jens Langhammer <jens@goauthentik.io> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jens Langhammer <jens@goauthentik.io>
3.4 KiB
title, sidebar_label
| title | sidebar_label |
|---|---|
| Integrate with engomo | engomo |
engomo
Support level: Community
What is engomo
engomo is an low-code app development platform to create enterprise apps for smartphones and tablets based on Android, iOS, or iPadOS. -- https://engomo.com/
This guide explains how to set up engomo to use authentik as the OAuth provider for the application login on the smartphone/tablet and login to the admin WebGUI (composer).
Preparation
The following placeholders will be used:
engomo.companyis the FQDN of the engomo install.authentik.companyis the FQDN of the authentik install.engomo.mappingis the name of the Scope Mapping.ak.certis the self-signed certificate that will be used for the service provider.
authentik configuration
In authentik, create a new scope mapping. To do so, log in and navigate to the Admin interface, then go to Customization --> Property Mapping and click Create.
engomo.mappingis the value of the Mapping's name.profileis the value for the Scope name.return {"preferred_username": request.user.email}is the value for the Expression.
Create an application and an OAuth2/OpenID provider in authentik. Use the following parameters for the OAuth2/OpenID provider:
Provider:
- Name:
SP-engomo - Client type:
Public - Redirect URIs/Origins (RegEx):
https://engomo.company/authandcom.engomo.engomo://callback/ - Signing Key:
ak.cert - Scopes:
authentik default OAuth Mapping: OpenID 'email', 'offline_access', OpenID 'openid'andengomo.mapping
Important
Redirect URIs => write the values line by line.
Leave the rest as default values. The durations can be changed as needed.
Application:
- Name:
engomo - Slug:
engomo - Launch URL:
https://engomo.company/
engomo configuration
Navigate to https://engomo.company/composer and log in with your admin credentials.
- Select
Server. - Select
Authentication. - Add a new authentication method by clicking on the plus icon on the right.
- Name:
authentik - Type:
OpenID Connect - Click Create.
- Set the
Issuerto the authentik FQDNhttps://authentik.company/application/o/engomo. - Set the
Client IDto the Client ID from the SP-engomo provider that you created in authentik. - Set the
Client Secretto the Client Secret from the SP-engomo provider that you created in authentik.
Leave the rest as default.
engomo user creation
engomo doesn't create users automatically when signing in. So you have to do it manually right now.
Navigate to https://engomo.company/composer and log in with your admin credentials.
- Select
Users & Devices. - Click the plus button next in the Users section.
- Select
authentikas the Authenticator in the dropdown. - Create your user by typing in the email as the Username used in authentik.
At this point you are done.
Test the login
- Open a browser of your choice and open the URL
https://engomo.company. - Enter the created user's email address and click the small arrow icon to log in.
- You should be redirected to authentik (with the login flows you created) and then authentik should redirect you back to
https://engomo.company/composerURL. - If you are redirected back to the
https://engomo.company/composerURL you did everything correct.
Important
The created user will only have access to the app or composer page if you granted the permission to the user of course.