Take the 2-minute tour ×
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It's 100% free, no registration required.

I don't know whether this issue is strange, but I am facing it first time. I am trying to create a publication target, which has a HTTP URL for HTTP Upload application. But I am not seeing any option for HTTP. There is HTTPS available, but it is asking mandatory login and password fields.

I am not sure what to do with it. Should I go ahead and modify the HTTPS Protocol Schema and make these fields non mandatory?

Please suggest. I am using SDL Tridion 2013

share|improve this question
add comment

4 Answers 4

My suggestion is not to change HTTP(S) Protocol Schema. As Login and Password is required for secured cases.

Its better to enter some dummy values in Login and Password fields. Ideally this should work.

share|improve this answer
2  
That's what I always do - just fill in dummy username & password - this will not be sent over the network unless there is an authentication challenge by the receiving deployer. BTW, you can use authentication on HTTP as well, but obviously you'd be sending the credentials unencrypted, which is not recommended... –  Nuno Linhares Apr 15 at 13:20
add comment

Yes, I believe you can edit the Schema and make them optional.

To quote the documentation on HTTP(S) Protocol:

"Although the transport method is called HTTPS, the use of SSL and of username/password is optional."

share|improve this answer
    
Thank You Very Much –  Sharad Sangal Apr 15 at 12:40
add comment

alternatively, If you want a option for HTTP in your drop-down, you can create it in

Publishing Management > Protocol Schemas

use this link for more info (login required)

share|improve this answer
add comment

Dummy values would work indeed for user name and password. The HTTPS protocol schema in Tridion works for both HTTP and HTTPS.

How sensitive is the content you are uploading? For sensitive content deployment, my opinion is not to ignore this and default to HTTP. More careful if your website and the http uploader application are not on the same server, and the packages have to travel some distances to reach the target.

In above cases a https would work better with a valid username and password. Like Nuno said, it is not a good idea to send clear username and password across the wire with http

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.