I have heard from some of the microsoft connect blogs that Geneva Server works with AD/LDAP as identity providers. If I have to configure my own custom attribute store in SQL server, with these users not being in AD groups would that be possible.from the blogs what I have seen is that Genevea Server is tightly coupled with AD and if I have to use custom store then I have to write my custom STS by overriding base classes from the Geneva Framework. So my question is is it possible to authenticate a user from the SQL store,(who is not in AD group) visa the Geneva Server Beta 2?
My mistake, a SQL attribute store is supported, but SQL account store is NOT supported in beta 2.
Yes, you can. MS has published a guide that shows you how, you can grab it (GenevaServerFederatedCollaboration-SBS-Guide.pdf) from here:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=57602615-e1ee-4775-8b79-367b7007e178
See the step titled "Using a SQL Server database as an alternative to using Active Directory or AD DS as a data store"
Related
Just want to know that I have my ASP.NET MVC application and related SQL Server database. I have signed up for a free Azure account.
I want to know if I can publish my app and database to Azure with this free account. The purpose of that, I want to check how the things are working properly and also since I working from home, selected user's want to see the progress of my project.
you need to have paid subscription for SQL server feature. Try finding SQL server express also know that SQL server will separately require you to pay SQL server license key. I would suggest to look into free SQL server hosting accounts instead of directly using Azure SQL server.
I want to publish my website on to azure, but the database should be on-premises for each client. One default database, however, should be on Azure too. In my asp.net MVC website, after my connection with default database is established, then I change the connection string based on the credentials entered by the user on login screen. This user database would be present at the client.
Do I simply change the connection string in web.config or do I need to set it up as follows?
I read this article that looks familiar to my scenario
https://learn.microsoft.com/en-us/azure/app-service/app-service-hybrid-connections
Should I follow this article directly or do I need to create "cloud service deployment" as mentioned in this article?
The SO thread you referred for cloud service deployment is very old.
Go ahead with Hybrid connections. Read best practices.
I have implemented Umbraco using UmbracoIdentity for membership and everything was going fine until I deployed my solution to an Azure Web App. On azure I am getting permission errors because UmbracoIdentity is using a SQL Server CE database stored in the App_Data folder.
For reference the error I am getting is:
Exception type: SqlCeException
There is a file sharing violation. A different process might be using the file. [ ...\wwwroot\App_Data\UmbracoIdentity.sdf ]
My Umbraco data is being stored in an SQL database and I would like to store my UmbracoIdentity membership data here as well. I would appreciate any help in how to setup SQL Server as the user store for membership data.
You need to implement the IExternalLoginStore.cs interface and then configure the application to use it. It should be fairly simple to implement as you can use the SQL Server CE implementation as an example. I've done one for Azure Table Storage - you can check the Readme at https://github.com/alindgren/UmbracoIdentity.AzureLoginStore to get an idea of how to configure the app to use a custom external login store (which for me was the least obvious part).
I am creating an iOS project that needs to read a SQL database in Azure. I have the database Server location, port, username, and password. I don't need to write to the database, just read it. I am more familiar with Firebase or Parse and have never used Azure. How do I even go about starting this? I tried the sample project that Azure makes for you but I don't have any tables? Do I need this? Any help would be welcome.
Azure Mobile App Service can connect with your existing SQL database
this thread explains the process where you use the existing SQL database. With this option Azure manages most of the inner workings for you.
If you want to build the Rest API from "scratch" using your existing SQL database You have some more options:
Azure API Management allows you to publish API's securely and at scale, A server less Azure Function like the example in this article Rest API with Azure Functions and Azure SQL Database or build a rest API using an Azure Logic App which doesn't require you to write code. You could also use Nodejs or many other tools you just need to evaluate what would work best for your use case.
So despite the warnings, I think I need to build a custom STS. We will support an arbitrary number of customers who provide identity information via SAML.
What is the best practice to store details on each IP? Most examples seem to store this info in the STS's web.config. That seems like it wouldn't scale real well.
Is there an obvious reason not to just store this stuff in a db and load it when the requests come in?
Fundamentally, if the Identity Providers will change over time, such as via some online administration function, rather than a new application deployment, it makes total sense to store the information in a database (or other Storage).
I think this is a potential issue for any multi-tenanted service that is federating identity with the customer.
ADFS v2.0 (which is Microsoft's STS product) stores its details in either a SQL Server DB (or SQL Server DB farm) or a Windows Internal DB. So if it's good enough for Microsoft ...