Anshul,
If the information is sensitive -> open a case
If you open a case, or are serious about getting help, you need to understand the following are absolutely necessary to share for people to know what you're doing and what capabilities you have:
Version of SiteMInder -- major version (eg: 12.0), service pack (eg 3) and cumulative release (eg 12)
What version of Java this is using (eg: 1.4)
This allows one to know "are you using the wrong version of java?" which is important as the Federation calls are highly version dependent.
By "highly version dependent" I mean that CA knows for a fact with how they write the federation calls, if it's not a version of java they certify the policy server with, it will fail in at least some cases.
Next there's detailing the issue. either do this with end to end logging, or by writing more than "what does x mean?"
even if I knew and told you what the 1 meant, it wouldn't help resolve the issue. we don't know the issue because you haven't told us the issue.
From what you have shared I would be more concerned with the line "SSO.java][processApplicationRedirect][No application URL defined - not redirecting.]"
and the line "[SSO.java][processAssertionGeneration][Received the following response from SAML2 assertion generator: SAML2Response=NO.]"
until these are resolved, it doesn't matter if you're authorized.
if you're not sure how to configure the traces, either enable EVERYTHING, or go here: https://communities.ca.com/thread/101076074
that should have a write up on logging that's nearly complete. I've put a ticket in for an update. more wouldn't hurt.
that being said, the next hurdle is learning how to correlate logs.
do you know how to do that or do you need your company to send you to training?
sorry for the phrasing, but log correlation is something they should be teaching in the SM 1 course....
-josh