Skip to main content

Windows Live - Web Authentication

Windows LIVE series:
Live ID se poate folosii pentru doua lucruri:
  • autentificarea userilor in aplicatia noastra folosind contul de Live ID
  • accesul aplicatiei noastre la servicii pe care un user de LIVE ID are access( photo sharing, agenda, calendar, etc)
Astazi o sa discutam despre cum poate un utilizator sa se autentifice in aplicatia noastra folosind contul de de Live ID.
Mai jos o sa prezint vechiul mod de autentificare, care a devenit absolute, odata cu lansarea "Live Connect", despre care o sa povestim cat de curand. Prefer sa prezint si acest mecanism in cazul in care lucrati cu aplicatii deja facute care folosesc vechiul mecanism de autentificare.
Acest mecanism de autentificare a fost denumit de cei de la Microsoft "Windows Live ID Web Authetification", dar nu are nimic mai special. In momentul in care userul doreste sa se autentifice, acesta este redirectat spre pagina Windows Live ID, unde isi va introduce datele. Dupa acest pas, userul este redirectat inapoi spre aplicatia noastra cu o cheie unica( token) - denumita Cliend ID, pe baza careia putem sa identificam userul. Pe langa aceste informatii, avem access la cateva date de baza a userului precum nume, tara, etc.
Cliend ID este o cheie unica formata din 16 caractere, pe care o sa trasmiteti la servere Windows Live de fiecare data cand un user se autentifica. Toate datele care se trasmit o sa fie encriptate si semntate pe baza unuei chei secrete pe care o primiti in momentul in care va inregistrati aplicatia.
Primul pas pe care trebuie sa il facem este sa ne inregistram aplicatia. Fiecare aplicatie se identifica unic pe baza unei chei. Acest lucru se poate face la urmatorul link: http://go.microsoft.com/fwlink/?LinkID=144070
Odata ce avem aplicatia inregistrata, trebuie sa adaugam in aplicatia noastra un link de autentificare prin Live ID. Acest link o sa contina ca si parametrii:
  • appid - cliend ID( cheia unica a aplicatiei noastre)
  • context -( optional) pagina spre care userul sa fie redirectionat dupa ce autentificarea se finalizeaza( ex. welcome.html)
  • style -( optional) o colectie de atribute folosite prin care se poate personaliza bunoul de sign in
Dupa ce userul isi introduce credentiale o sa fie redirectionat spre pagina noastra. Pe flowul normal, in cookies o sa gasim un token encriptat cu cheia "webauthtoken". Acesta o sa contina urmatoarele date despre user:
  • User.Id – id-ul unic a fiecarui user
  • User.Timestamp – data ultimei autentificari
  • User.Context – contextul care a fost specificat in momentul autentificarii
  • User.Token – token-ul unic a userului curent( dupa o anumita perioada de timp acesta o sa expire)
Trebuie precizat ca datele sunt encriptate este AES128, iar cel de semnare este HMAC-SHA256. Mai jos gasiti un exemplu de cum trebuie facuta decriptatea si extragerea datelor.
public string DecryptResponse(){     const int ivLength = 16;     token = HttpUtility.UrlDecode(token);     byte[] ivAndEncryptedValue = Convert.FromBase64String(token);     var decryptAlg = new RijndaelManaged();     decryptAlg.KeySize = 128;     decryptAlg.Key = cryptKey;     decryptAlg.Padding = PaddingMode.PKCS7;     var memStream = new MemoryStream(ivAndEncryptedValue);     byte[] iv = new byte[ivLength];     memStream.Read(iv, 0, ivLength);     decryptAlg.IV = iv;     cStream = new CryptoStream(memStream, decryptAlg.CreateDecryptor(),                          CryptoStreamMode.Read);     sReader = new StreamReader(cStream, Encoding.ASCII);     return sReader.ReadToEnd();}

In urmatorul post o sa discutam despre Live Connect.

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…