Solution : https://service.sap.com/sap/support/notes/654982 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues where MYSAPSSO2 cookies are not set despite correct browser settings and secure HTTPS connections that fail due to invalid certificate names. When specifying URLs, ensure they include the domain to comply with cookie specifications, which vary depending on domain extensions. For HTTPS, the SSL certificate Common Name (CN) must match the host name in the URL to avoid errors. Ensuring correct domain specifications and SSL certificate details will resolve these issues and help maintain secure and functional server communications.
Key words :
web server/sap web application server/sap j2ee server, sap web application server security, sap web application server, ou=sap trust community, penultimate domain components consists, checked ssl server certificate, national top-level domains, ssl scheduling reverse proxies, cookie specification rules listed, ssl server certificate
Related Notes :
| 1257108 | |
| 1009930 | (Display) problems in View Designer when you load a view |
| 945516 | Web Dynpro ABAP in a portal environment |
| 830830 | Inf. broadcasting: Typical problems with folder selection |
| 817529 | Checking the SSO configuration |
| 805344 | How URLs are generated automatically in BW |
| 763427 | Error message for domain name with underscore |
| 701205 | |
| 677118 | SP31-> Fully Qualified Domain Names Check |
| 654326 | Domain restrictions in a portal environment |
| 632440 | Domain barrier in the browser of the SAP Enterprise Portal |
| 612670 | |
| 611361 | Hostnames of SAP servers |
| 585042 | Reduction of the data transfer Web middleware/browser |
| 517860 | Logging on to BSP applications |
| 356691 |