Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Publishing and non-secure URL's

  Asked By: Sonny    Date: Jul 07    Category: Sharepoint    Views: 1014

Once I publish a page I would like it accessible from http://url because
people are going to be accustomed to just typing in "url" in the address
bar, which defaults to http.

However, I do not want content contributors to be tempted to log in from
a non-secure site and compromise their credentials. Has anyone else had
this problem?

Is there anyway to display or hide the sign-in button based on whether
the url is http or https?

Is there a way to force the signin URL to always direct to https:// ?

Is there another way that would be better?

Share: 

 

6 Answers Found

 
Answer #1    Answered By: Jonathan Thompson     Answered On: Jul 07

It's called content  Deployment.

blogs.msdn.com/.../content-deployment-step-by-ste\
p-tutorial.aspx

 
Answer #2    Answered By: Taylor Mills     Answered On: Jul 07

I am attempting to deploy the content  on our production server to a
test server (virtual), in order to duplicate the environment we
currently have in production. (We're a little backwards, I know)

I used the step-by-step instructions found below, after having
unsuccessfully set up a content deployment, and I still received the
same results as my first try:

I set up the path and the job. When I run the job, the status
remains at "preparing" and never gets any further. Any insight on
how to overcome this would be greatly appreciated.

 
Answer #3    Answered By: Angel Jordan     Answered On: Jul 07

We also ran into that same issue, though we were going from dev to prod.
But the answer for us was to create a blank site  on the server you are
moving to and then setup the jobs to move the content.

 
Answer #4    Answered By: Darrell Peters     Answered On: Jul 07

I did do that, but the jobs for some reason never
complete/succeed. They don't officially "fail" either, but they just
get stuck in the "preparing" queue. Is this also what happened to
you? I'm not sure if it has anything to do with SSL or what...I have
no idea what's causing it to "hang up".

 
Answer #5    Answered By: Lester Casey     Answered On: Jul 07

Check the temp location for the job. Is there sufficient disk space to
package the site. content  Deployment "packages" the content locally in a
temporary location, pushes it to the destination server which places it
in a temporary location and then unpacks it into the local farm
database. Insufficient files system storage is a frequently overlooked
problem.

 
Answer #6    Answered By: Rudy Francis     Answered On: Jul 07

If you just want to keep Content Contributors from contributing when
they come in via an HTTP:// address then there is another way. Assuming
you have setup the alternate addresses by extending an existing Web
Application to create a Zone and not just added an Alternate Access
Mapping you can create a Web Application Security Policy that denies
write access to users who access the system through the HTTP:// zone.

That won't remove the Sign-in, but if you leave that Web App set to only
allow Windows Integrated Authentication then they will only be able to
use a secure Authentication (encrypted) mechanism to log  in through that
site.

 
Didn't find what you were looking for? Find more on Publishing and non-secure URL's Or get search suggestion and latest updates.




Tagged: