Thanks Wolfgang for brief explanation.
If we keep "No for Legacy Logon ticket then, issue #5 happens. The work around was to setup "Yes" for Legacy.
After above setting, Issue#5 on reoccur, when we have PPM NWBC (tab 1 in below screen) already running in same browser and open FIORI Launchpad.It prompt for the user id and password. I don't understand why NWBC running for PPM should have conflict with FIORI. The only workaround is to identify each service and bump up "SAML " login module.
For Issue # 6.
Below is the architecture flow.
FIORI SP -> Siteminder IDP ( SAML) -> FIORI Launchpad -> Backend ECC (Trusted RFC)
PPM NWBC ITS User id and pwd -> ECC (Trusted RFC)
Therefore I don't understand why SAML Authentication has to conflict with PPM MYSAPSSO2 for the Issue#5. They both are on same domain .. Is that an issue?
For session timeout handling, FIORI SP does request re-authentication from IDP but it is frame in frame. Please advice if we can avoid it.
Thank you in advance.
Santosh Lad