Web dynpro application url changes from http to https on transport.

[matt]

In Dev, web dynpro applications have a url http://., in Test, it is also http://., but on import to Prod it is https://...

On Dev and Test the parameter login/ticket_only_by_https is set to 0, on Prod it is 1 - so maybe connected to that?.Being just an 'umble programmer, I don't get to change parameters on the customers's systems. My Basis team think it's a development issue - I'm trying to avoid a ping-pong between departments.

[former_member221408 · Accepted solution]

Is the issue only with the logon or is the application itself called with HTTPS protocol?

If the application is called with HTTPS protocol, there are two places where it can be controlled:

1. tr. SICF: /default_host/sap/bc/webdynpro/sap... -> 'Logon Data' tab -> 'Security requirement'. Standard or SSL.

2. tr. SE16, table 'HTTPURLLOC', where it can be set differently in the systems.

What you can also do, is to check if this is issue only for your WD Application, or any other web based services. E.g. try to call transaction SOAMANAGER, and see if this is opened also with HTTPS protocol in Prod.

[raymond_giuseppi]

Could you navigate to the service /default_host/sap/bc/webdynpro/sap... there display your service, select 'Error Pages' tab, click on 'Configuration' at the bottom of the window, in 'System Logon Conf.' look at Protocol value (drop/down list) in 'Actions During Logon' block. It could be 'Swith to HTTPS' in your case?

[matt]

Did that. All identical in the three systems.

[pokrakam]

I think your only_by_https is very likely part of the picture. You can also look at SMICM, 'Services' button (3rd one) to see if http is even enabled.

[matt]

http and https are both active on all systems.

Also odd is that the basis chap, when he looks at the main view of a webdynpro in production, he gets prompted for a logon (and we have password-less SSO, so doesn't get to see the preview of the view), and I don't.

[pokrakam]

Do they get a different http/s variant?

I don't have the answers, but I also don't understand the problem - which part of the behaviour is undesirable? I'm also pretty sure this has nothing to do with the webdynpro application, but is either the SICF service or the networking layer.

A system can be set up to automatically switch http to https (I forgot where, but could even be that parameter). A simple test is to disable https in SMICM and then it should connect via http with a pw prompt. Obviously this is just a brief change to try out the theory.