11-17-2011 06:11 PM
Integration Response Rejections
We're unable to get a response XML (see attached) accepted by the IS. Any thoughts?
Here is the log:
2009-May-01 18:45:10 GMT
Channel=agent
Level=WARNING
LogID=1972
Thread=File listener thread for agent 'AD_Integration'
Error (agent 'AD_Integration'): XML request from third party is not parseable! Status code = -210
org.xml.sax.SAXParseException: Content is not allowed in prolog.
at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
at com.celosis.XMLBase.deserializeDOMTree(XMLBase.java:69)
at com.celosis.eai.papi.agents.file.FileAgent.onFileMessage(FileAgent.java:472)
at com.celosis.eai.papi.agents.file.FileAgent.run(FileAgent.java:387)
at java.lang.Thread.run(Thread.java:534)
Thanks!
11-17-2011 06:11 PM
James, you find out what it was?
11-17-2011 06:11 PM
make sure the msg comes in on 1 line
11-17-2011 06:11 PM
Hi James:
I am interested in how you are adding the AD Groups into RequestCenter.
So far we are only using the default OU with our users.
Thanks
11-17-2011 06:12 PM
Hi Morgen,
Those were just in the XML generation. Get rid of the line breaks in the XML and you should start to see these go away.
Thanks!
11-17-2011 06:12 PM
Hi James,
We're doing automatic network provisioning now - it's very cool. I'd be happy to share some info on it. We're going to address AD group memberships (and through that, application installs) later this year.
Re: the prolog error, we're seeing that in our logs also; you mentioned it was line breaks - were these occurring in the data values, or just in the XML generation?
Thanks
11-17-2011 06:12 PM
Hi Emir,
Sorry I neglected to post back. Yeah, it was primarily the line breaks. We then had a couple of other issues, but have it all working now.
We're building out a POC and are going to move forward on a pilot within the next few weeks. We're going to use ServiceLink to automatically add AD group memberships and possibly in the future use it to auto-provision new network accounts.
Thanks for helping out!
11-17-2011 06:12 PM
The AD groups are staying in AD. We're using service requests to grant or remove membership to the AD group that would apply for that service.
We haven't implemented anything with LDAP nor do we use LDAP lookups.
What is it that you're looking to do?
Thanks!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide