SEC Agent: REST call: HTTP header "Authentication" has been removed by RMP

76 views
Skip to first unread message

olli.pe...@gmail.com

unread,
Apr 6, 2018, 8:29:45 AM4/6/18
to Fujitsu RunMyProcess Developer Community
We are using the SEC connector for executing JIRA REST calls over the SEC Agent. This fails because the HTTP header "Authentication" has been removed when the request arrives at the SEC Agent. All other custom header attributes arrive at the SEC Agent and are used for the REST call.

Removing the HTTP header "Authentication" before sending the request to the SEC Agent looks like a bug to me.

Regards
Oliver

Pankaj Kumar

unread,
Apr 6, 2018, 8:12:20 PM4/6/18
to Fujitsu RunMyProcess Developer Community
Hi Oliver,

Please send more details of SEC configuration and JIRA REST service invokation (Some screen-print)  required parameter. You can send those information to me on "pku...@runmyprocess.com" if those are  not general information to share.

Also kindly let me know your availability on call on hangout to troubleshoot the issue.



Thank you,
Pankaj Kumar
Fujitsu RunMyProcess Support


--
Fujitsu - RunMyProcess
---
You received this message because you are subscribed to the Google Groups "Fujitsu RunMyProcess Developer Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to supportforum+unsubscribe@runmyprocess.com.
To post to this group, send email to suppor...@runmyprocess.com.
Visit this group at https://groups.google.com/a/runmyprocess.com/group/supportforum/.
To view this discussion on the web visit https://groups.google.com/a/runmyprocess.com/d/msgid/supportforum/bc6302e2-b0c0-4336-8c74-01654f0c864a%40runmyprocess.com.
For more options, visit https://groups.google.com/a/runmyprocess.com/d/optout.

Pankaj Kumar

unread,
Apr 10, 2018, 4:54:40 AM4/10/18
to Fujitsu RunMyProcess Developer Community
I replied privately to user.

Thanks,
Pankaj Kumar

Pankaj Kumar

unread,
Apr 10, 2018, 5:52:41 AM4/10/18
to Fujitsu RunMyProcess Developer Community
Hi Oliver,

As discussed, issue is related to provider configuration. It is resolved providing the authentication scheme (login/password) in provider authentication scheme option.

Thanks,
Pankaj Kumar
Reply all
Reply to author
Forward
0 new messages