How can i integrate Sharepoint authentication into my BPOS setup? i want users to login to Sharepoint using the same credentials they use to login to BPOS. This is to avoid having to use seperate FBA for Sharepoint 2010.
Do note that the Sharepoint i used is Sharepoint 2010 enterprise and not Sharepoint Online.
Thanks
Depends a bit on your scenario and if you are using identity federation.
If you are federating your identities to the cloud/office365 using DirSync then you have SSO to both on-premise and SSO.
If you only have MSOnline users, ie no AD on-premise or at least not syncing it, then you need to set up your on-premise SP2010 with claims support and set up a trust relationship with the Office365/SPOL STS. (At the moment since Office 365 is in private beta and under NDA - that's about what I dare to share...but it's doable)
Related
I have a SharePoint Online application that access an API the reside outside my network and one of our Azure. This API is accessibly through public. I am using this API to access data in my SQL server, with this I am worried that my API is not secure and I am wonder what are the things I can do to secure my API so that no only users logged in to our SharePoint can use it.
There are several ways in which you can secure it. These ways vary in complexity and each have their specific considerations.
Secure an API with Azure AD
If you're using Office 365, securing custom APIs using Azure AD is an architectural option that you should definitely consider. First and foremost, it allows you to secure the access to the API using existing organizational credentials that are already managed through Office 365 and Azure AD. Users with an active account can seamlessly work with applications that leverage APIs secured with Azure AD. Azure AD administrators can centrally manage access to the API, the same way they manage access to all other applications registered with Azure AD.
More info: here
I am new in dealing with Sharepoint Server and other office services. Sorry if my question doesn't make sense. My question is:
Can I use other authorization servers other than azure ACS as an access token issuer for Sharepoint 2013 apps ?
I would like to apply OAuth authentication mechanism to the SharePoint sites which are currently accessible by enabling basic authentication of site properties.
SharePoint 2013 supports for server-to-server authentication and app authentication by utilizing and extending the Open Authorization 2.0 (OAuth 2.0)
I am trying to have app authentication to access sharepoint resources(site users) with OAuth mechanism. Is it necessary to register my app on Azure ACS just to get OAuth tokens. Can I also use other auth server which can generate OAuth access token. If yes, how will they app, custom auth server and sharepoint communicate each other?
I am trying to get multiple identity providers (Google, Facebook, multiple ADFS) working with a SharePoint 2013 web application provisioned on Office 365.
I know about options related to ADFS and Shibboleth, but am wondering if there is any way to get Azure ACS to handle the authentication for this web app. I do have an on-premise SharePoint 2013 web application working with Azure ACS, but don’t have much info around how to do the same thing with Office 365 or if it’s even possible.
Not supported (yet).
Given that Office 365 use Windows Azure AD, we can hope that ACS support will come one day.
I am trying to evaluate a strategy where I can integrate our Azure based application to SharePoint Online.
The idea is to provide seamless UI so that they are able to use the best of the features from both these applications without having to navigate away from our application.
We would like to bundle the application with Sharepoint online so that if a user comes to our application they will see another tab for collaboration which will open SharePoint online in a seperate iFrame or something like that.
However the issue here is that we do not want the user to keep another set of user credentials for SharePoint online. Is there a way where we can provide some kind of single sign on here.
Our application uses forms based authentication.
I could verify that you sure can use ClaimBased SSO with Azure and SPOnline. Look for the following:
Claims-Based Single Sign-On for the Web and Windows Azure
Remote Authentication in SharePoint Online Using Claims-Based Authentication
So using Claim Based Authentication (Use Windows Azure ACS) you can merge SP online and Azure Web Role together.
I need to implement a web application hosted on sharepoint. This is a client requirement. So I cannot create a standard asp.net web application. Another client requirement is that the authentication is not an active directory one but they want to use an existing database of users.
I am a bit concerned how this would work on sharepoint because users would need to log-in onto sharepoint. Would it make sense that users log into sharepoint as anonymous and then we use our custom controls for log-in. How does sharepoint handle anonymous users?
Any assistance would be greatly appreciated
When building apps over SharePoint, you use the SharePoint authentication mechanism, whatever it is.
Does the SharePoint farm is already in place ? Or do you have to also build the farm ?
In the former case, probably the authentication mechanism is already in place and you just have to build a "standard" sharepoint application.
In the later case, you will have to carefully plan your authentication. SharePoint can use a combination of AD authentication, Forms authentication (over a DB in your case if you want) or a Claims authentication pattern. My guess is that a Forms authentication with a custom Membership/role provider is the way to go.