[
https://issues.apache.org/jira/browse/GUACAMOLE-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Couchman closed GUACAMOLE-706.
-----------------------------------
Resolution: Duplicate
This is resolved in GUACAMOLE-1507, where the "extension-priority" property was
added to the Docker startup script.
> Configure order of authentication extensions being loaded in docker container
> -----------------------------------------------------------------------------
>
> Key: GUACAMOLE-706
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-706
> Project: Guacamole
> Issue Type: Improvement
> Components: guacamole-docker
> Affects Versions: 1.1.0
> Reporter: Jörn Lentes
> Priority: Minor
>
> To combine authentication extension for RADIUS with database authentication
> extensions it is required to change the order of extensions being loaded.
> Since by default extensions are being loaded alphabetically and extensions
> are called in the order loaded, the name of the RADIUS authentication
> extension needs to be changed when the docker container is created.
> *Solution:*
> I propose that each auth extension introduces an environment variable that
> lets you define the name of the symbolic link created in the start script of
> the docker container.
> {{RADIUS_EXT_LINKNAME=1-guacamole-auth-radius}}
> The script adds the file extension .jar to the name to avoid an extension not
> being loaded at all.
> That way you can influence the execution order of extensions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
