Workflow Soluiton

 View Only
Expand all | Collapse all

Problem with AD integration after publishing

  • 1.  Problem with AD integration after publishing

    Posted May 12, 2010 12:30 PM

    I create a wobform that use GetUserDetails Compoment. When I use degug method the values is showed normally. But after the publish the workflow, the fields dont show values.

    Its necessary any configuration after publishing?



  • 2.  RE: Problem with AD integration after publishing

    Posted May 12, 2010 03:14 PM
    Are you using the Get Current User component?  This functions differently when deployed then it does in debug.

    Also, are you deploying to the same server you are developing on?  Differences here can affect how you connect to the AD server.




  • 3.  RE: Problem with AD integration after publishing

    Posted May 12, 2010 03:48 PM
      |   view attached

    Yes, I am using Get Current User before component Get user Details.

    I am developing in same server (on Workflow Server).

    Can you help me? The file is attached.

    Attachment(s)

    ZIP
    FAIL_AD_DEPLOYMENT.ZIP   1.91 MB 1 version


  • 4.  RE: Problem with AD integration after publishing

    Posted May 12, 2010 06:06 PM
    The problem is that

    After publication the aplication get "Network Service" as logged user. I trust that have any problem because the component is not  get correct information.

    Can be any problem in Virtual Directory configuration?


  • 5.  RE: Problem with AD integration after publishing
    Best Answer

    Posted May 13, 2010 11:41 AM
    There is a great video explaining the setup of the Get Current User component here : http://www.workflowswat.com/components

    Y
    ou'll need to configure your process in IIS to not allow anonymous access, as well as changing the security type in the web.config file to be "Windows".  Lastly, you'll want to set the component to HTTP Context when deployed, and Environment when debugging.  There are some easy ways to add a small embedded model at the start of each process that will function correctly regardless of being deployed or in debug.  If you want me to show you send me an email at aaron@wevogroup.com and I'll setup a time.

    Good luck,
    Aaron


  • 6.  RE: Problem with AD integration after publishing

    Posted May 13, 2010 09:42 PM
      |   view attached
    Thanks Aaron,

    I changed the option in Get Current User component to Windows method. After incluse to component to remove domain Information.

    This way the problem is solved in publication.

    Thanks again,

    Everton


  • 7.  RE: Problem with AD integration after publishing

    Posted May 13, 2010 09:42 PM
    Thanks Aaron,

    I changed the option in Get Current User component to Windows method. After incluse to component to remove domain Information.

    This way the problem is solved in publication.

    Thanks again,

    Everton


  • 8.  RE: Problem with AD integration after publishing

    Posted May 18, 2010 09:11 AM
    am having the same problem after publication with authentication method as "Windows Principal" in component tho Get Current User after publication.
     

    In first tests is run normally, but the problem occour again.
     


  • 9.  RE: Problem with AD integration after publishing

    Posted May 18, 2010 09:30 AM
      |   view attached
    Set the 'User Name Type' dropdown in the Get Current User component editor to "HTTPContext" when publishing to the server. See below for an example.



  • 10.  RE: Problem with AD integration after publishing

    Posted May 18, 2010 09:37 AM
    The one thing I'll add is that "Http Context" will return both Domain and Username ie "CompanyDomain\User1".   The use of the Split Text Into Collection component will allow you to remove just the username, which is what's commonly needed when working with AD components.