Sign In   Register
Pinned Items
Recent Activities
  • Upon first submission of a form by a user we trigger a Job Task Assign action:


    {
    "name": "Referee",
    "type": "",
    "actions": [
    {
    "name": "Assign Review",
    "type": "Job Task Assign",
    "properties": [
    {
    "name":...
    Upon first submission of a form by a user we trigger a Job Task Assign action:


    {
    "name": "Referee",
    "type": "",
    "actions": [
    {
    "name": "Assign Review",
    "type": "Job Task Assign",
    "properties": [
    {
    "name": "Task Assign Email",
    "value": "$formDataMap.RefOneEmail|$formDataMap.RefTwoEmail"
    },
    {
    "name": "Task Form Code",
    "value": "$func.startFormCode()"
    },
    {
    "name": "Task Form XML Data",
    "value": "$func.stepOrPreviousSubmissionXml()"
    },
    {
    "name": "Task Attachments Submission Step",
    "value": "Application Start"
    },
    {
    "name": "Task Send Email",
    "value": "true"
    },
    {
    "name": "Task Type",
    "value": "Anonymous"
    },
    {
    "name": "Task Assign Repeating",
    "value": "true"
    }
    ]
    },
    {
    "name": "Review Wait",
    "type": "Job Task Wait"
    }
    ],
    "routes": [
    {
    "name": "Default",
    "nextStep": "Deliver Submission"
    }
    ]
    }


    which assigns a task to 2 different reviewers in parallel. We want to process the Delivery of each completed review task as they arrive rather than waiting for both to complete via the "Job Task Wait" and then performing an action. So, according to the config above we want "Deliver Submission" to actually run for each task immediately that it completes. Is this possible? How might we go about doing it?

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
  • Matthew White's reply was accepted as an answer
    It turns out that this was due to the lookup user not being found for the given ldapSearchBase. Unfortunately TM gives you the same error 'Bad Credentials' for both an incorrect service account username/password combo and also for a user not...
    It turns out that this was due to the lookup user not being found for the given ldapSearchBase. Unfortunately TM gives you the same error 'Bad Credentials' for both an incorrect service account username/password combo and also for a user not being found against a search Base, this took some time to get to the bottom of as I thought that the service account was failing for some reason.

    Can I suggest as a future update that Manager be more explicit in the error messages about what is failing and why, specifically to distinguish between the service account bind failing vs the user not being located due to an invalid search base.

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
  • It turns out that this was due to the lookup user not being found for the given ldapSearchBase. Unfortunately TM gives you the same error 'Bad Credentials' for both an incorrect service account username/password combo and also for a user not...
    It turns out that this was due to the lookup user not being found for the given ldapSearchBase. Unfortunately TM gives you the same error 'Bad Credentials' for both an incorrect service account username/password combo and also for a user not being found against a search Base, this took some time to get to the bottom of as I thought that the service account was failing for some reason.

    Can I suggest as a future update that Manager be more explicit in the error messages about what is failing and why, specifically to distinguish between the service account bind failing vs the user not being located due to an invalid search base.

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
  • I can successfully bind to the ldap server using the same credentials using code inside the groovy console. The windows account that the groovy code runs as is the 'computer account', e.g. myhost$

    Is it possible that the code in the ldap...
    I can successfully bind to the ldap server using the same credentials using code inside the groovy console. The windows account that the groovy code runs as is the 'computer account', e.g. myhost$

    Is it possible that the code in the ldap authenticator is running under the 'system' account (because JM is installed as a service and runs as system) and that this account is not allowed to bind to AD regardless of the credentials supplied.

    If someone from Temenos could confirm that groovy code executes as a different account than JM java code that would be helpful in troubleshooting this.

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
  • Hi Sergey

    Journey Manager is 21.5.1 in our dev env. Prod and Test with working LDAP are 5.1.10. I've managed to turn on debug logging and get this:

    2021-10-21T15:04:40.748AEDT DEBUG...
    Hi Sergey

    Journey Manager is 21.5.1 in our dev env. Prod and Test with working LDAP are 5.1.10. I've managed to turn on debug logging and get this:

    2021-10-21T15:04:40.748AEDT DEBUG [com.avoka.fc.core.security.LdapUserDetailsAuthenticationProvider] (default task-1) Authentication for *********** failed:javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C09044E, comment: AcceptSecurityContext error, data 52e, v2580

    The DN and password are definitely correct as I've tested them in multiple other applications.

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
  • Hi

    I'm getting a Bad Credentials Error when authenticating to an ldap (Active Directory) server from an ldap authenticator in Journey Manager. I can write custom groovy code that runs from the Journey Manager console to authenticate (bind)...
    Hi

    I'm getting a Bad Credentials Error when authenticating to an ldap (Active Directory) server from an ldap authenticator in Journey Manager. I can write custom groovy code that runs from the Journey Manager console to authenticate (bind) successfully but the same parameters don't work from the authenticator. How can I enable debugging/logging for this module in standalone.xml?

    This has worked on previous TM versions.

    ldap.jpg

    Matt
    More
    1. View Post
    0
    0
    0
    0
    0
    0
    Post is under moderation
    Stream item published successfully. Item will now be visible on your stream.
There are no activities here yet
Unable to load tooltip content.

Not a member?

Register to ask a question and access to more content.

Join now

Looking for something else?

You can request access to:

  • Courses
  • Full Release Notes
  • Product Downloads
  • SDK

Request access