• State Not Answered
  • +1 person also asked this people also asked this
  • Replies 3 replies
  • Subscribers 8 subscribers
  • Views 3583 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Can we call the JAVA API from outside Appian?

Jacob Edelman
A Score Level 3

We have a customer security provider that will tell us a user's authorizations.  Is there a way for our security provider to call the JAVA API to update a user's group memberships upon login?  Our other option is to build a process model that processes these authorizations for the user and to expose it as a Web API, WS, or JMS, so that can the security provider can call it upon login and then wait for it to complete before forwarding the user to Appian (concerned about execution time and successful completion and error handling).

  Discussion posts and replies are publicly visible

  • 0
    Appian Employee
    Technically, yes. In practice, I would advise against it as it requires you to essentially have another Appian install to have all the prerequisites.
    Few thoughts/questions:
    1. Does this have to be done on login? You will need a batch user synch anyway to capture any changes in case the user does not log in. See community.appian.com/.../identity-management for more info.
    2. If the synch needs to happen on login, it gets quite a bit more complicated but I would still use WebAPI over any other pattern. Assuming you have the user logging in directly to Appian (not from an external portal, etc.) you can set the user start pages to a WebAPI. The web api can start a process that completes all the work and then forwards the user where he truly needs to go. This assumes that either the user exists, or you are using SAML and can create the user on login. If the user does not exist and you cannot create them on login, you will need an intermediary to first call a web api to create the user (and also potentially do all the other work), then forward them to where they need to go. The overhead is going to be a few seconds on first login, otherwise you can likely short-circuit most of the work on subsequent logins.
  • 0
    A Score Level 3
     in reply to Mike Cichy
    We will be having the user login through a 3rd party authentication portal. We may have custom code do the user creation in the 3rd party portal. We are not going to use SAML, but OAuth for login. OAuth will be capturing the user's authorizations and need to forward them onto Appian so their user groups can be updated to match the authorizations.
  • 0 in reply to Mike Cichy

    Hi Mike, what can I do to forward a user to a particular Appian URL in a process model? In this instance, when user logs in, a web API will be executed that will in turn execute a process and at the end of that process I want to send a user, say to tempo. How would I do that? Is there a smart service that allows me to send a user to a particular URL?

© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.