cancel
Showing results for 
Search instead for 
Did you mean: 
newbie123
Occasional Member - Level 2

The remote server returned an error: (500) Internal Server Error

This AM I am getting "The remote server returned an error: (500) Internal Server Error" when trying to get access token from https://www.concursolutions.com/net2/oauth2/accesstoken.ashx

 

Is anyone else facing similar issues? I know they SAP were retiring a few SSL ciphers this week not sure if this is related .

 

 

 

 

1 Solution
Solution
newbie123
Occasional Member - Level 2

SAP never explained this discrepancy in fact no one knows how this happened but my educated guess during the week when ciphers were getting retired legacy authentication broke & this was at a point of no return. Closing this out as we have moved beyond these mishaps that as customers we are getting used these disruptions quite frequently now with no explanations.

View solution in original post

3 REPLIES 3
KevinD
Community Manager
Community Manager

@newbie123 are you still having this issue? Did you try a different browser?


Thank you,
Kevin
SAP Concur Community Manager
Did this response answer your question? Be sure to select “Accept as Solution” so your fellow community members can be helped by it as well.
newbie123
Occasional Member - Level 2

Yes I posted more details in another thread ...pasting the contents of it below..it's so frustrating that sap hasn't responded yet.

 

The remote server returned an error: (500) Internal Server Error

I started getting the following error while trying to get token (C#, .Net platform) since yesterday 

https://www.concursolutions.com/net2/oauth2/accesstoken.ashx

Error returned is this, The remote server returned an error: (500) Internal Server Error.

 

Support is telling me this legacy authentication is no longer supported & we have to start using oath 2. We were never informed of this decommissioning. Is there a bulletin about this? This is ridiculous that SAP has removed these without properly communicating to its customers. 

 

I looked at latest SAP release notes  & legacy authentication should be supported until Dec 2023, here is the proof below,

  

 

 

Token were fetched for the following 2 services,

 

https://www.concursolutions.com/api/expense/expensereport/v2.0/Report
https://www.concursolutions.com/api/expense/extract/v1.0

 

Does anyone know if these 2 services still work?

          •  
             

newbie123_0-1676595395951.png

Solution
newbie123
Occasional Member - Level 2

SAP never explained this discrepancy in fact no one knows how this happened but my educated guess during the week when ciphers were getting retired legacy authentication broke & this was at a point of no return. Closing this out as we have moved beyond these mishaps that as customers we are getting used these disruptions quite frequently now with no explanations.