Hi Reza,
If the issue persists, we will need to investigate further to narrow down the issue, whether it is with the ABAP server, J2ee, tickets, etc:
1) Clear all the browser cache.
2)
Set the security trace level in the ticket accepting system (r/3 server)
======================================================
1. Call transaction SM50 (process list):
2. Process -> Trace -> Reset -> Workprocess Files
3. Key combination: F5 (select all), CTRL-Shift-F7 => Dialog box;
4. Set trace level=3 and ONLY(!) check the "Security" component;
If necessary, you must repeat these steps for each server (see
transaction SM51), unless you can use a specific server for
reproducing the error (for example, by excluding the load
distribution).
3)
Run the web diagtool as outlined in: note 1045019 (example 1).
4)
While the diagtool is running, please reproduce a failed SSO to
the backend.
5)
When the SSO fails, wait a minute and then press return in the
diagtool console so that the resulting traces are picked up.
6)
Attach the html diagtool log, the j2ee server default traces, SM50 trace and step by step screenshots of error reproduction to the message.
7)
Specify the time at which you reproduced the issue and the userID
involved.
8)
Attach the screenshots of the TCode /nSTRUSSSO2 and the ACL.
The error that you are facing is mentioned in great detail in:
SAP Note No. 1769367 - Issuer of SSO ticket is not authorized
You can also use the below link to search for the specific error in the R/3 traces.
http://scn.sap.com/docs/DOC-57078
_____________
Kind Regards,
Hemanth
SAP AGS