Issues on 2023.2.17.0 with variables expansion

Resolved

Issues on 2023.2.17.0 with variables expansion

avatar

Hello,

We have noticed that in version 2023.2.17.0 (and the previous one, at least) a bug has been introduced in expanding variables in certain contexts. We don't know if it has any relation with the issue, already reported, of $PARENT_HOST$ not being expanded. This time we noticed that using the $DOMAIN_NAME$ variable in this User Interface option:



results in the following misbehavior:



This occurs also with the $DOMAIN_DOMAIN$ domain and possibly other domain related variables. We don't remember to have noticed this issues with versions 2023.1.x

Thanks!

91cabbf6-c422-469e-aa72-d3a3d0f8ea93.png

7b6cec63-6327-4efb-b5f3-f6365278ef5d.png

All Comments (4)

avatar

Thanks for reporting this issue, we are looking into a fix asap. Please let me know if you spot any other issues in Active Directory or have any other feature requests we would be happy to add them!

Paul

avatar

Hello,

Can you confirm that the Active Directory Console connection entry is inside a Domain Folder? I tested with 2023.2.17.0 as well as 2023.1 and could not reproduce the issue. The $DOMAIN_NAME$ variable appears to come from the name of the Domain Folder that the connection is inside of. All the $DOMAIN_* variables are inherited from the parent Domain Folder. If you want to access the domain name from the connection entry you use the $DOMAIN$ variable. See screenshot below:



Maybe there is another factor in your configuration that is causing it, as my example is very simple with one Domain Folder and one connection.

Thanks for your patience while we work to find the cause of this issue.

Paul

84a6d04b-3bd3-409b-a6cd-3e0a6a08113c.png

avatar

Hello Paul,

You are right, the Active Directory entry isn't anymore located in a domain folder, my bad. The fact is that once you've extended the vault settings in incorporating the feature request regarding the UI settings, we removed the Domain folder (which was the only direct child of the vault, as we have a separate vault for each domain) because it was unneeded with the new UI settings in place. We had completely forgotten about the Domain folder removal, and we've been biased by the fact the $PARENT_HOST$ variable is not being expanded properly in the current version.

I apologize for the false bug report. I am sorry for the confusion.

Thank you!

avatar

Thanks I'm happy we found your problem, Please reach out to me if you have any other feedback on our Active Directory implementation.

Best regards,
Paul