Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
2 replies
Subscribers
6 subscribers
Views
1323 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Process
Why doesn't third party authentication work inside an HTTP QUERY node in a p
davidj578
over 9 years ago
Why doesn't third party authentication work inside an HTTP QUERY node in a process model:
ERROR INFO:
Title: Failed to retrieve value from SCS username=, Message: com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException: com.appiancorp.suiteapi.common.exceptions.AppianException: An error occurred while accessing the per-user credentials from the Secure Credentials Store. The encryption key for [ ] was not populated during login. See the documentation for proper configuration when using a custom authentication provider. (APNX-1-4221-001), Details: An error occurred while accessing the per-user credentials from the Secure Credentials Store. The encryption key for [ ] was not populated during login. See the documentation for proper configuration when using a custom authentication provider.
while it works within a rule:
a!httpQuery(
"API",
"GET",
{a!httpHeader(
"Connection",
"keep-alive"),
a!httpH...
OriginalPostID-194017
OriginalPostID-194017
Discussion posts and replies are publicly visible
0
davidj578
over 9 years ago
...eader(
"User-Agent",
cons!browsers),
a!httpHeader("Accept", "*/*"),
a!httpHeader("Accept-Encoding",
"gzip, deflate, sdch"),
a!httpHeader("Accept-Language",
"en-US,en;q=0.8")},
a!httpQueryParameter(" "),
a!httpAuthenticationBasic(
username:a!scsField(
externalSystemKey:"[ ]",
fieldKey:"username",
usePerUser:true),
password:a!scsField(
externalSystemKey:"[ ]",
fieldKey:"password",
usePerUser:true()),
preemptive:true()
)
)
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Nick Vigilante
Appian Employee
over 9 years ago
There is an issue with the way the Http Query node is being handled. This is actively being investigated by our product team. I unfortunately have not been able to find a workaround for this, other than to disable usePerUser.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel