It seems this functionality was broken :( Could you please file JIRA? On Fri, 17 May 2019 at 13:33, Maxim Solodovnik <solomax...@gmail.com> wrote:
> Will try to double-check the code > > On Thu, 16 May 2019 at 02:03, R. Scholz <rene.sch...@abakus-edv-systems.de> > wrote: > >> ... and the port defined in the base-url. >> >> >> >> Am 15.05.2019 um 17:53 schrieb Scholz, Rene: >> >> Hello Maxim, >> >> it ever uses the base-url from the configuration for generating the link. >> >> Best regards, >> >> René >> >> >> >> >> Am Mittwoch, den 15.05.2019 um 12:20 schrieb Maxim Solodovnik: >> >> Hello Rene, >> >> If I do remember correctly current base URL (retrieved via JS >> callback) is used while invitations generation >> So this should work as follows: >> >> 1) user A access OM at port 5443 >> 2) generates the link (send invitation) >> Result: base URL has port 5443 >> >> 1) user B access OM at port 5444 >> 2) generates the link (send invitation) >> Result: base URL has port 5444 >> >> Can you check if it works for you? >> >> On Wed, 15 May 2019 at 13:48, R. Scholz >> <rene.sch...@abakus-edv-systems.de> <rene.sch...@abakus-edv-systems.de> >> wrote: >> > >> > Hello, >> > >> > I want to access my OM-instance over 2 Subdomains. >> > One subdomain use port 5443 (with the correct certificate) the other >> > over port 5444. >> > >> > When I send an invitation the link-generator use the setting in the >> > OM-configuration. >> > Thats clear. >> > >> > My Idea: >> > Is it possible to implement "a wildcard" so the invitation-link use the >> > invoking address? >> > Or is it possible to implement different URL-settings for different >> port? >> > Or any other idea? >> > >> > With best regards, >> > >> > René >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> >> > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
