Users

All Posts (9)

avatar

Mehdi

OTP-Entry for M365 MFA Accounts - The application and account may not contain the ':' character.

avatar
avatar
avatar
avatar
avatar

Hello,

Is it not possible to automatically replace the character both internally and in the entry?

Or just interpret it internally and not show this error when editing the entry?

We have a lot of entries that we update regularly, and it is tedious to have to replace the characters on all of them...

Best regards,

OTP-Entry for M365 MFA Accounts - The application and account may not contain the ':' character.

avatar
avatar
avatar
avatar
avatar

Hi Zachary,

We have the same problem since the updating, before this update the character was accepted, and it must be accepted because it is the default format for many OTP configuration...

Do you have any update on this?

Thanks,

Logon loop with Microsoft authentication starting from version Version 2022.3.26.0

avatar
avatar
avatar
avatar

Hi Richard,

The problem is that we are working on a VDI environment, so this option mean that the users will need to enter their UPN in every host. And for the upgrade we are using a rdi file, maybe the configuration will be overwritten?

Anyway, I have a ticket open, I will ask if it's possible to return the result of "whoami /upn" command on the data source settings or as before the upgrade have the choice to not fill this parameter.

Thank you for your time

Logon loop with Microsoft authentication starting from version Version 2022.3.26.0

avatar
avatar
avatar
avatar

It doesn't seem to work with the $USER_PRINCIPAL_NAME$ variable:

As for variable concatenation, this does not work in our case since the %username% variable refers to the profile path name and not the exact UPN prefix:

%username% = FirstnameLastname (no dot between the first name and the last name)

UPN (Whoami /UPN) = Firstname.Lastname@domain.abc

Thanks,

Logon loop with Microsoft authentication starting from version Version 2022.3.26.0

avatar
avatar
avatar
avatar

Hi,

We are facing the same problem, in our case the problem came from the data source settings, in the old versions it was not mandatory to fill in a user, on the new version it became mandatory.

No matter what information is filled in, it cannot be changed once on the login page

And the problem is that the username variable (%username%) does not return the UPN on an Azure AD joined machine so it can't be used.

As it is, we cannot deploy the new version unless we ask each user to modify the data source manually, which is not an option....

Best regards,

Problème d'affichage en RemoteApp via VDI en Windows 11

avatar
avatar
avatar

Effectivement, j'ai essayé d'activer/désactiver cette option mais cela ne change rien au problème.

Problème d'affichage en RemoteApp via VDI en Windows 11

avatar
avatar
avatar

Bonjour,

Merci pour votre retour, néanmoins le problème ne concerne pas une entrée RDM, mais l'affichage de l'application RDM en elle-même.

RDM n'est pas installé sur nos postes, nous l'utilisons en remoteapp via une VDI et lors de cet usage l'affichage en plein écran de l'application RDM est décalé.

Cela est peut-être lié à ce sujet remonté il y a quelques années sur le forum ?

Cordialement,

Problème d'affichage en RemoteApp via VDI en Windows 11

avatar
avatar
avatar

Bonjour,

Nous utilisons RDM via Azure Virtual Desktop (VDI), et depuis la migration de notre infrastructure virtualisée vers Windows 11 nous rencontrons des problèmes d'affichage avec RDM en remote app.

La fenêtre est mal calibrée lorsque nous essayons de l'agrandir en plein écran, elle est décalée et une bordure blanche apparait sur les côtés :

Le problème n'est présent qu'en remote app, via la session distante (full desktop) il n'y a pas de problème.

Le constat est le même que ça soit à partir d'un client windows 10 ou 11 et RDM est la seule application ayant ce comportement en remote app.

Cordialement,

Ability to set default vault permissions

avatar
avatar
avatar
avatar
avatar

+1

We have the same issue. With 77 Vaults, global settings changes are starting to become time consuming.

This feature is essential, especially for MSP contexts.

And i hope that this feature will not be limited to the "System Permissions" but will also be implemented for all the Vaults settings like Session Recording.

Regards,

1 - 9 of 9 items