Loading
search-img

MajaHamer asked a question.

September 13, 2021 at 3:29 PM
AD group as an identyfier in Automation Platform- issue.

We have set up an Automation Platform for users to request access to applications. We want to automate access to applications available in Citrix. The workflow is set up in a way where user is added to relevant AD group which this gives him access to application- he has it in his Citrix workspace. I wanted to add the application recently for users to request via automated workflow. But when we import the application to Automation Platofrm we get an error: Identifier (AD group) is already assign to another applicaiton. It turns out that AD gorups are reused when our teams are upgrading application packages and transfer them to Vidisk image. Is there a way to overcome this is AP workflow? Does anyone uses similar logic ?

  • 9 answers
  • 74 views

  • Community Manager (Flexera Software)

    Are you sure you cannot save the setting anyways? For me, I do get the warning, but I am still able to save in SLM. There should be nothing stopping you from running the import after that as far as I know.

    Selected as Best

  • AxelLa

    I haven't found a way to override this.

     

    On the other hand, regarding versions as separate applications is a SLM specific behavior.

    I assume, the endusers im most cases do not care for the version. They need an application to do their work and it is up to IT to define the versions used in the environment.

    So, what we did is to make apoplications available in AP without version numbers. Additionally, we have established a process how to "activate" a new version, like:

    • remove the AD group entry from the old version in SLM (I think you need to save this before the next step)
    • remove the "available in software store" checkbox on the old version in SLM
    • make the new version available in the software store

     

    Sometimes I'd like to have multiple services using the same AD group, but as mentioned above I haven't found a way to achieve this.

    Expand Post

    • MajaHamer

      Thanks for this Axel. I will try applying this before upgrading SLM to the latest version, as sugested below.

  • Community Manager (Flexera Software)

    Are you sure you cannot save the setting anyways? For me, I do get the warning, but I am still able to save in SLM. There should be nothing stopping you from running the import after that as far as I know.

    Selected as Best

    • Oskar Frolin (Flexera Software)

      I did not know this had changed, but it seems to be corret. Just confirmed in latest available SLM that it only gives you a warning that it is already in use. Earlier versions did not allow it.

       

      //Oskar

  • AxelLa

    You can save it in SLM, but the Import Script in AP will report an error.

    Noitr 100% sure though, it's been a while since I have checked this.

    • Community Manager (Flexera Software)

      I cannot find that logic in my version of the script. It could be that you are using an older version perhaps. Anyways, you can always modify the "import slm applications.ps1" script if you want.

       

      If you could post a screenshot of the error I can have a look as well

      Expand Post

      • AxelLa

        Not sure what version I have testes the last time, probbly you are correct.

        I have modified the script, but this is at least a year ago.

      • MajaHamer

        Hi,

         

        I will need to upgrade SLM , it seems. Thanks.

Related  Product Forums


                     → Flexera One



                      → Snow Atlas



                      → FlexNet Manager



                      → Snow License Manager



                       → App Broker


       Need help finding an answer?


        Ask a Question →


+1.800.374.4353
CONTACT SALES SUPPORT HUB FLEXERA REVENERA
© 2026 Flexera. All rights reserved.
Privacy policy Terms and conditions Revenera Community Help
Loading
AD group as an identyfier in Automation Platform- issue.