[IdP] "Object reference not set to an instance of an object" error

[IdP] "Object reference not set to an instance of an object" error

  
Forge Component
(26)
Published on 4 Jul by Telmo Martins
26 votes
Published on 4 Jul by Telmo Martins

We are getting an "Object reference not set to an instance of an object." error in Service Center when the user request a single logout. Actually for each request for single logout two lines with the same error are generated at Service Center logs, as the details bellow:


First error

Time of Log: 22/11/2018 15:54:02

eSpace: IdP

Module: 

Message: Object reference not set to an instance of an object.

Environment Information: 

eSpaceVer: 44 (Id=17664, PubId=17606, CompiledWith=10.0.900.0)
RequestUrl: https://somedoain/IdP/SLO.aspx (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/IdP-4321-131866049137394014
FilePath: C:\...\PS\running\IdP.1556661045\SamlSLO.aspx
.NET: 4.0.30319.42000

Stack: 

Object reference not set to an instance of an object.
   at ssIdP.RssExtensionXml.MssXmlElement_GetInnerText(HeContext heContext, Object inParamXmlElement, String& outParamInnerText)
   at ssIdP.Actions.ActionRetrieveMessageIDsFromSamlMessage(HeContext heContext, String inParamSamlMessage, Boolean inParamGetIssuer, String& outParamMessageId, String& outParamResponseId, String& outParamIssuer)


Second error

Time of Log: 22/11/2018 15:54:02

eSpace: IdP

Module: Extension metho

Message: Object reference not set to an instance of an object.

Environment Information: 

eSpaceVer: 44 (Id=17664, PubId=17606, CompiledWith=10.0.900.0)
RequestUrl: https://somedomain/IdP/SLO.aspx (Method: POST)
AppDomain: /LM/W3SVC/1/ROOT/IdP-4321-131866049137394014
FilePath: C:\...\PS\running\IdP.1556661045\SamlSLO.aspx
.NET: 4.0.30319.42000

Stack: 

Object reference not set to an instance of an object.
   at OutSystems.NssXml.CssXml.MssXmlElement_GetInnerText(Object ssXmlElement, String& ssInnerText)
   at ssIdP.RssExtensionXml.MssXmlElement_GetInnerText(HeContext heContext, Object inParamXmlElement, String& outParamInnerText)


Despite the error, the logout process are finished successfully, I mean, user's sessions is endded on Outsystems and on Identity Provider, in our case OpenAM. 


We need to worry about these messages? Do you have seen this before?


Thank's,


Tiago

Hi Tiago,

On the first error that's the whole stack error? The remaining stack is needed to check if it was while checking the logout request or logout response.

The error itself it's due it cannot retrieve the Issuer from the message. In the saml message logs the messages are all without error?

Also the Logout is initiated by the IdP connector or IdP server?

Regards


Hello Telmo,

It is the complete stack error that Service Center logs show me; there is another placte to get a full version?

In the saml message logs there is no error; I can see a logout request and logout response, both valid. 

The logout is initiated by SP, in this case, the IdP connector.

Best regards

Hi Tiago,

Ok, in that case only through debug on that action it will be possible to understand what's causing that, and on which screen flow are we.

Regards