The material provided is for informational purposes only, and should not be relied on in making any purchasing or investment decision. The information is not a commitment, promise or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion. © 2026 Cloud Software Group, Inc. All rights reserved
Hi Norbert,
Thank you for your note.
I know about it. But this is not a case in our situation. We use existing AD groups a nd there are no name convention.
Before version 4 we were able to sort list in Administrative Console. It allowed to check if this AD group wasn't added already.
I'm not sure if you are aware that starting from Spotfire Server v6.0 it was possible to use wildcard characters for matching AD group names. This for us has completely eliminated the need to change the config file for adding a new AD group as we use a specific group naming convention, so all new AD groups are automatically picked up by the server as soon as they are created and synced. See release notes for 6.0: https://docs.tibco.com/pub/spotfire_server/6.0.0-november-2013/TIB_sfire_server_doc_6.0.0_relnotes.pdf (page 4, other enhancements)