I've been investigating some localization issues with our web application and even though I start to understand the problems and the way to solve them... I still have a couple of questions I failed to find a decent answer to.
It would be great of some people can point me out to appropriate documentation for me to read up and understand more the concept of ApplicationPoolIdentity.
What I understand so far:
There are 2 ways to make your web application Localization-aware based on your requirements.
1) Configure in the web.config file (Globalization) or in the IIS UI for the specific website.
This works great, except it does not pick up Globalization on IIS-level when website is Auto Detect or Invariant Culture? What's the hierarchy it's using?
2) Configure Localization for the user under which the IIS process is running.
You need to copy the Localization settings to the system accounts (as explained here)
You then need to run the apppool under one of these accounts (local, Networkservice, LocalService...)
It does not seem to work when running under ApplicationPoolIdentity
ApplicationPoolIdentity is a virtual user account, assuming that's why it's not picked up by the copy-to action in Localization.
Although, it's not working either when I say Copy-To-New-Accounts.
So what Localization is the ApplicationPoolIdentity using???
It seems the default one based on the Windows Installation, am I right here?
If anyone can correct me and answer my questions, or link to some more documentation around this. Really appreciated.
Related
I'm trying to learn a few things about SharePoint and I would like to figure out what do I have to do to make my content available online so I can access it from my other computer in my work / home so I can add documents to it.
I did some research on how to set up websites on IIS and setting up my DNS host on Windows Server 2012 with some demo html files I've made. I tried to do research online with port forwarding but I can't find info clear enough for me to get the job done.
Could somebody maybe give me some direction on where to look and a checklist on what I need to complete this task? I feel like I'm shooting in the air trying to figure this out. I've never really dabbled in this before.
Here are some resources you might find useful in getting this setup. It's difficult to say exactly what you need to do without knowing what it is you've already done.
I haven't watched through the channel9 video but according to the description it includes how to setup internet facing sites in an on-premise environment.
Providing SharePoint is up and running, it should just be a case of configuring the Alternate Access Mappings for internet access, DNS and Port Forwarding.
https://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC390
https://blog.blksthl.com/2012/12/03/a-guide-to-alternate-access-mappings-basics-in-sharepoint-2013
The final guide to Alternate Access Mappings
I think that this is an usual question, but I'm reasking it cause I didn't got a real good question.
So, I have Liferay 6.1 CE running on Tomcat 7, and I want to import the users from an LDAP server and then make an SSO with CAS.
In my Portal, I have other application integrated (here also I have a problem with the integration of Alfresco) who need to be logged in also with the credantials from LDAP, this is why I need an SSO solution, like CAS.
How can I face this issue ? is there anyone who could help me fixing all this ?
Any information can help me, I have to accomplish all this in two weeks...I hope that everything that I'm asking are feasible.
Thanks & Regards
Liferay provide all necessary infrastructure to resolve your requirement. Look for CAS and LDAP at portal.properties https://github.com/liferay/liferay-portal/blob/master/portal-impl/src/portal.properties and configure this in your portal-ext.properties Liferay: How to configure Liferay Portal
You have two tasks here, importing users from LDAP and authenticating users with CAS. You can configure both from the Control Panel (UI) or the portal-ext.properties file. If you configure using both methods and there's a property conflict, the Control Panel settings take precedence.
Importing users from LDAP isn't difficult (I've done it in both 5.2.3 and 6.1), although importing/not importing the password can be confusing. Try tackling this task first and make sure you're able to authenticate against LDAP. I'd recommend using an authentication chain (multiple means of authentication where if one method fails, a second method will be attempted, and so on). It would be useful to configure it this way in the event of an outage with CAS so you don't have a single point of failure. Note: If you use portal-ext.properties, be sure to read this post and add properties mentioned (even if you aren't going to use them):
ldap.user.custom.mappings.1=
ldap.contact.mappings.1=
ldap.contact.custom.mappings.1=
Regarding authentication against CAS, I've been using it for a couple years on Liferay 5.2.3, and in my experience it's worked very reliably.
I'm trying a long time to get a working SQL connection in my web part. I read a lot of msdn stuff and tried many things, but I can't get it working... Every time I try to open a SQL connection, my web part throw an exception: Request for the permission of type 'System.Data.SqlClient.SqlClientPermission.
I tried custom.configs which set the .net trust higher, edit the manifest, set the permissions with the PermissionSet-Class and also tried FullTrust, but nothing worked. How do I set the permission correctly?
Btw, the web part is a sandbox solution.
It would be awesome if someone could give me a detailed view, how to set the permissions.
For this kind of operation, You need to develop a full trust proxy(SPProxyOperation) to be used by your Sandbox Solutions.
The sandbox solutions has Code Access Security and Permission restrictions. For details you can visit:
http://extreme-sharepoint.com/2011/10/07/sharepoint-sandbox-reallly-new-feature/
Does anyone know of a complete, downloadable/copyable example of a WiX installer that allows the user to select an existing website when installing a web application?
I'm trying to get this working and, after seeing that it seems to be a significant piece of work, I'd like to get an example running first so that I have a working project to base my own work on.
I found this (code is pasted as images) and this (can't get it running).
Just to confirm... Is it really as much work as the sites above suggest to allow a user to select the site to install to? Am I missing a trick?
I found this blog post that does the custom action in C# and has a complete downloadable sample. Pretty easy to follow.
Yes, that would be quite a bit of work to do it in WiX. I don't typically give a user this much choice. You might just want to do it as an after install configuration step if it's important to you.
Is there a way to get URI based access control directly in IIS that works with static content, ASP, WCF services and anything else that comes in looking something like an HTTP request?
Particularly I want the access control to be a bullet proof as possible preferably making the decision before IIS even tries to figure out what to service the request with.
This link sort of hints that this can't be done but it's old and I'd be very surprised if what I'm looking for doesn't exist.
This link has a few other options (and a less "aggressive" community)
An ideal solution would be able to declare that everything (static and dynamic content) under a given URL (for example https://dns.name/some/path/*) needs a login and the user must be in some group. Also, I'd rather set it up with a username/passord file (at least for now) rather than AD or some windows account system.
In short I want access control and I don't want to be writing code to get it.
This seems related but I'm not sure it's quite the same.
You can set access rules for ASP.NET or WCF web application in web.config file.
HOW TO: Control Authorization Permissions in an ASP.NET Application
If you have access to IIS and you know .htaccess syntax, you can use ISAPI_Rewrite 3. The Lite version is free.