I'm using Office 365 and Windows Azure. I need to create an App on Azure that will require authentication and will be accessible for Sharepoint workflows.
I created simple ASP.NET app that uses Azure Active Directory for single sign-on (according to this steps: http://www.asp.net/identity/overview/getting-started/developing-aspnet-apps-with-windows-azure-active-directory )
Then I created workflow on Sharepoint, that calls this App and retrieves response content. Unfortunately it turns out that instead of website content it returns login page.
My question is how to make the connection between Sharepoint Workflow and Azure App, so that the App would require to log in for users, but would be accessible for the Sharepoint Workflows?
Sorry for my poor explanation, but I'm very new in this topic.
Related
I have a web application, and I am looking to make use of SharePoint endpoints using the user's Windows credentials. SharePoint 2013 does not have CORS support, so there is no way for me to send XHR requests to SharePoint from my web page, which is hosted separately from SharePoint.
My thought is then to create a separate WebAPI based web service that uses Windows Authentication. Taking those credentials, I can then make use of the CSOM and pass those credentials through to pull back data from SharePoint with the permissions of the impersonated user.
Is this possible? I have tried several variations, but I have not been able to get it to work.
After looking through multiple tutorials and posts, I have not found an answer or guide as to how to handle the following issue:
There is an Azure API App communicating with an Azure DocumentDB
There will be an Azure Web App (and some day mobile apps) communicating with the API App.
I would like for anonymous users to have access to read only information through the Web App (and only through the Web App). The
API App will serve up documents as requested. Anonymous users
connecting directly to the API App should not be allowed to retrieve
any information.
For contributors, they will be able to add documents using the Web App
when they are logged in. The documents will go through the API App
to be written to the DocumentDB
What are the suggested ways for handling anonymous users and authenticated users so both can use the Web App and the underlying API App successfully while blocking any use of the API App if it does not come from the Web App (or future mobile apps)? I only want anonymous users to be able to retrieve information when using the Web App.
The API App is developed in C# .NET 4.5, and the Web App will be the same. I'm not planning on writing my own authentication since the Azure Gateway takes care of this, but it only has the options of Public (Anonymous), Public (Authenticated), and Internal. Public (Anonymous) lets everyone in, while Public (Authenticated) blocks the anonymous users that I would like to have read only access. I'm very new to dealing with Authentication so I'm not even sure if this is possible without having to write my own authentication engine.
For clarification, this question is purely for Authentication between the Web App and the API App.
Thanks,
There is Sharepoint 2010 intranet portal with several intranet sites based on Active directory user access. Is it possible to create one more site with quite different security model for Internet access or should I create standalone portal for Internet users? What shall I consider?
You can have different authentication models at "Web Application" level. This means that all your site collections inside your Web Application will work with the same authentication model.
If you already have a web application working with Active Directory and you want to provide Internet Access (probably using Forms Authentication) you will need to create a separate Web Application.
Here is a sample Video on how to create a new Web Application:
http://www.youtube.com/watch?v=0Z8vb42j1wQ
And this is a video on how to implement Forms Authentication a Web Application:
http://www.youtube.com/watch?v=yBqL3E-ne60
I've been looking at this so long now that I think I'm probably missing something obvious. My scenario is this.
I have a SharePoint 2013 app which needs to pull data from a set of web services (not SharePoint hosted) to populate the application. Because the SharePoint server and API server are hosted in the same domain and authenticate against the same AD server, what I would like is for the user to sign in to SharePoint and then use the same credentials to make the request to the API server. It's a SharePoint hosted app, so the request needs to be made via JavaScript (well, using jQuery).
I'm guessing that this is possible, but what's the best way to look at implementing it.
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.