I have an excel file that has data connections linked to SharePoint.
It asks for credentials to connect to SharePoint
I already have a VBScript in place that refreshes the excel automatically and saves it.
Is there a way in which I can embed the credentials and enter into the pop-up.
I am new to VBScript. Any help is appreciated.
Can you embed the credentials? Probably. The real question you should as is should you? If anyone were to gain access to your script, they would have the username and password to a domain account (or even a domain admin account if that is what you are using). Not good.
I using IMsgServiceAdmin::ConfigureMsgService to configure a outlook profile for my exchange server.
When calling this function, windows will popup a dialog to enter the credentials. After I enter the credentials and save, I found it will create a Generic Credentials : MS.Outlook:#.:PUT and the password is encrypted. Such as "##...yBA"
I would like to how does outlook encrypt my password as I want to manually create the credentials before I call ConfigureMsgService so that the credentials windows won't show.
Thanks in advance.
I'm a Senior Escalation Engineer for Outlook here at Microsoft and received this exact question from a customer in the past. We asked the product team if they would be able to document the format used to publish credentials in credential manager. The answer is, no, we can't, because we routinely change the format as new scenarios crop up. It may not be obvious, but the target name of the credential will be different for different scenarios. That's the critical part. Without knowing all of the details for constructing that target name, knowing how to protect the password won't help you.
For Outlook 2010 and below, use CryptProtectData(). The data to protect is a Unicode string containing the password. The length of the data (in bytes) is 2*length of the password in chars excluding terminating 0x0.
For Outlook 2013 and up, CryptProtectData is not used - CredWrite takes the password.
I have the TFS power tools installed, and I can see the shell extensions context menus; however, I can't find a way to bypass the integrated windows authentication and specify a new username per operation. I am using a common username on a server due to some legacy software, and I need to access TFS with a different domain user. Is there an option to do this on the fly?
I expected to receive a prompt when connecting, but I just get an error indicating that the current user doesn't have permissions.
If you want to ALWAYS use a certain user name & password when authenticating to a TFS server then you can use Windows Credentials Manager and add a new Windows Authentication entry. You type in the full server name, domain username, and password. Additionally, you'll want to add the server name into the "Trusted Sites" list in Internet Explorer.
Just remember to edit that entry in the future if you ever need to change it like when the account's password has been updated. You'll be pulling out your hair until you remember that it is in there.
Our environment is Sharepoint 2010, with a web application created (and site collection on top), using claims based authentication. The first site is using port 881. It is using integrated windows authentication. Another web application is created, extending the first application, using port 882. This site is using Forms Based Authentication, the membership provider is System.Web.Security.ActiveDirectoryMembershipProvider, named admembers. I have turned off Client Integration on both sites.
When I login to the 881 site, on my corporate network, logged into the machine with the same domain account that sharepoint uses, I can open an Office file saved in a document library, and it subsequently opens in the appropriate Office application, without asking me login again. But, If I login to Sharepoint from a computer that is not on our network, or login to the computer with an account that is not a domain account, I get prompted again to login when openning an Office document. If I choose the option to save, it does not prompt, but if I choose open in the dialog window, I am forced to enter my domain credentials again.
When I login to the 882 site, which uses FBA, I experience the same problem. If I open an Office document, the appropriate Office application opens, and asks me for my credentials, by showing me a dialog window with the sign in page loaded. If I choose to save the file, then I am not prompted to login, and the file saves to a local folder.
I can't expect my users that are off site to login again everytime they open an Office document, like Work, Excel, Powerpoint, etc. I have tried numerous fixes, including disabling client integration, changing the browser handling mode (strict/permissive), changing internet explorer settings (for integrated windows authentication), changing the integrated windows authentication site to use basic authentication, even hacking the page using jquery to call the sharepoint javascript function that execute the "download a copy" function. None of them work: when choosing to "open" the Office document in the browser, the user has to login again, or just close the dialog window without logging in (as long as client integration for the zone is turned off).
I'm looking to get this accomplished using windows authentication or forms based authentication.
Help!
I found this answer in a similar post which seemed to fix the problem for me when I tested it. The gist of it is you need to deny the HTTP Verbs OPTIONS and PROPFIND in IIS. Having said this, I'm not an IIS guru and am not exactly sure what this means or what else it might affect. Can anyone else shed some light on this?
A bit of background, I'm using SharePoint 2010, on an FBA site.
You have the standard three use cases:
Employee intranet access
Employee remote access
Partner remote access
Employee intranet access
This normally always works out of the box, and it looks like it is working for you.
Employee remote access
The only way that i have seen this work (and i have tried many ways) is to get TMG or ISA. Basically ISA is setup in FORMS auth with SSL, it captures the auth details, and then passes them to the sharepoint server. (and other servers if you have them eg OWA for sharepoint mail web parts)
If you select the "Is private computer" option on the ISA login screen, then Office documents share the auth cookie and don't prompt for another login. I had so many problems, but as soon as i installed TMG, they all went away. I would not recommend any other approach now.
The added bonus of this method, is that remote employees are treated as the same account as the intranet user. The way you are setup with a seperate web application, means that they will be different accounts, so things like [checkout/modifiedby/createdby/personalisation] will be different accounts (though they look the same)
Partner remote access
This may never ever work on some clients (especially Vista), as IE needs to share the authentication with Office
If this is sharepoint 2010, try this.
Get-SPSecurityTokenServiceConfig
Look at your UseSessionCookies value in the output. If True, apply the powershell below.
$sts = Get-SPSecurityTokenServiceConfig
$sts.UseSessionCookies = $false
$sts.Update()
If UseSessionCookies is true, you will have to login to any docs u want to download...
Hopefully someone can help...
I need to provide client with a solution to allow bulk creation of user accounts into SharePoint SSO. The client wants to provide an excel spreadsheet with accounts, usernames and passwords and have that created in the SSO database.
I've been told its possible but I can't see how and google is failing me. I've been told its "some custom development and the SharePoint object model". As far as I can see all of the credentials stuff in the Microsoft.SharePoint.Portal.SingleSignon namespace is very much read only.
I have a solution which is to get them to save the spreadsheet as a CSV file and to use jmeter to squirt the data in through the front end. I don't think that's really an acceptable solution though.
Anyone got any clues? Or can anyone say definitively this can't be done?
Thanks in advance...
You can store the user credentials in Active directory or SQL database based on the authentication method. You can write code for copy these credential in the AD/database.