Tranquil IT Forum

Hello,

Having recently implemented the WAPT solution, we are still getting to grips with the tool, as we currently only have the trial license.

We tried associating groups from our Active Directory (AD) with a Self-Service package, carefully following the online documentation.

However, we noticed that when the AD group name contains special characters (in our case, spaces and underscores), it doesn't work; users in the group don't have access to Self-Service. But with a group whose name doesn't contain special characters, it works fine.

Is this the problem? Could someone please guide us?

Thank you,

Have a good day!

I just tested it here with spaces, and I don't have any problems. Could you try renaming the group to verify that the issue is indeed caused by the spaces/underscores?

Simon

Hello,

I'm a colleague of anmartin's. We ran more tests this morning and indeed the problem isn't with spaces or underscores.

However, we have groups containing parentheses, and these are what's causing the issue (see attached).

Are you experiencing the same problem on your end?

Valentin

Note that parentheses and spaces are replaced with tildes (~) in the console for the self-service rule name.

Valentin

I've never tried using parentheses

in your wapt-get.ini configuration; are you in waptserver-ldap mode?

An internal issue has been identified with the waptserver-ldap mode.

It will be fixed in the next version. Thank you for reporting the bug!

This is fixed in the latest release; I'm marking the topic as [RESOLVED].
Regards,
Denis