Jump to content
Welcome to our new Citrix community!

Daniel_Theis

Members
  • Posts

    3
  • Joined

  • Last visited

About Daniel_Theis

  • Birthday 03/22/1982

Profile Information

  • User name display option
    User name

Daniel_Theis's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Hi Carl, thanks for this hint. Using SAML worked fine from the first moment on. 🙂
  2. Good morning, I'm new in the world of Citrix DaaS, but the environment is up and running fine when we use our Azure authentication. We have a subscriptions with Cloud Connectors, a working FAS environment and desktops running in Azure. People can start desktops; Single Session, Multisession, no issue. We connected Okta as an IDP, followed the guideline and after changing the authentication method in the Workspace configuration to Okta, I can successfully log in and authenticate with Okta, and I can see the resources. To be able to see the resources, I have to use the Okta identity on the desktop resources. When I try to start a resource then, I get the error: "No workstation available", although machines are running and registered. If I set the following option during the creation of the Delivery group, I can start the desktop with Okta, but the system does not seem to recognize me as an AD user, as it tries to log on with a local user to this machine, which does not work of course. Did anyone encounter this so far, and does anyone have an idea, why the authentication is successful ( first step) but the start of the resource not? Have a good day!
×
×
  • Create New...