Appian Ingration that is called within Appian

erickp over 5 years ago

I created an Appian Web API that given a user, returns all the application roles the user is part of. This API will be used within Appian itself (I created the API because basic users can't execute the plugin function getgroupsformemberuser so I am bypassing the security in this fashion).

I went ahead and started creating the Integration object and when I attempted to test, I got the error: This request requires Basic authentication, but no credentials were provided HTTP/1.1 401.

Does every HTTP Integration requires a Basic Authentication? If so,

1. What is the best practice in this regards? Should I create an Appian service account for this?

2. When am I able to select Authentication = NONE?

3. Is there another way to do this type of integration by using a Connected System?

Discussion posts and replies are publicly visible

Parents

0 Robert Shankin
Appian Employee
over 5 years ago

Hi Erick -
Right now, Appian web API's do require preemptive basic authentication.

Are you familiar with the Modify Process Security Smart Service?
docs.appian.com/.../Modify_Process_Security_Smart_Service.html
Perhaps a solution that leverages this smart service would work.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 erickp over 5 years ago in reply to Robert Shankin

Hi Robert, in my use case I don't have a process model but a report itself within a Site. As you are aware, if I were to have a process in a Site, I would need a Start Form and I am trying to stay away from that. I made an update to the question - do you know if there is any other way to avoid creating a web api for this scenario?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Robert Shankin
Appian Employee
over 5 years ago in reply to erickp

I would probably use a start form, but I'm not clear on your use case.
Under what circumstances does a non-sysadmin end user need to see all the groups that they're in?
Are all the groups going to make sense to the user?

I would hope that this is a report that's only viewed very rarely.
Assuming it only viewed infrequently, I think it's reasonable to trade an extra single click (to run the process) for a much simpler design (that doesn't include an API).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Robert Shankin
Appian Employee
over 5 years ago in reply to erickp

I would probably use a start form, but I'm not clear on your use case.
Under what circumstances does a non-sysadmin end user need to see all the groups that they're in?
Are all the groups going to make sense to the user?

I would hope that this is a report that's only viewed very rarely.
Assuming it only viewed infrequently, I think it's reasonable to trade an extra single click (to run the process) for a much simpler design (that doesn't include an API).
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

0 Robert Shankin
Appian Employee
over 5 years ago in reply to Robert Shankin

There are those who might like to use the API call, though:
community.appian.com/.../configuring-appian-web-apis
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 erickp over 5 years ago in reply to Robert Shankin

We have a user access recertification process that runs once a year and our audit department needs to view the current membership for all of the Appian users so we are building an Appian report for them.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel