locked
CAS SSO for Asp.Net website, attributes not receiving on serviceValidate request RRS feed

  • Question

  • I have successfully integrated CAS for our different clients. But this time 'samlValidate' response is not consistently supplying the required attribute. Login is failing randomly because of the missing attribute in the ticket validation response. Sometimes when I clear browser history, it's receiving the attribute in the response.

    Expected response:

    <cas:serviceResponse xmlns:cas='http://www.xxxxx.xxx/tp/cas'>
        <cas:authenticationSuccess>
            <cas:user>xxxxx</cas:user>
            <cas:attributes>    
                  <cas:userId>1234567</cas:userId> 
            </cas:attributes>
        </cas:authenticationSuccess>
    </cas:serviceResponse>

    Response receiving randomly:

    <cas:serviceResponse xmlns:cas='http://www.xxx.xxx/tp/cas'>
        <cas:authenticationSuccess>
            <cas:user>xxxxxx</cas:user>
    
    
        </cas:authenticationSuccess>
    </cas:serviceResponse>

    Please share your thoughts to resolve this issue. Thank you in advance.


    Sreekanth Mohan

    Tuesday, February 27, 2018 2:33 PM

All replies

  • Hi Sreekanth Mohan,

    Thank you for posting here.

    For your question is more related to ASP.NET, you could post a new thread in ASP.NET forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions.

    Best Regards,

    Wendy


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, February 28, 2018 5:58 AM
  • Introduce the following setting in the cas.properties:
    cas.view.cas2.v3ForwardCompatible=true
    

    That’s it.

    See more: https://apereo.github.io/2017/06/23/cas-protocol-compatibility/

    Wednesday, October 24, 2018 9:59 AM