Skip to main content

Windows Live - Web Authentication

By
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.
Labels:

Comments

Post a Comment

Popular posts from this blog

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

By
The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...
Post a Comment
Read more

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

By
Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...
Post a Comment
Read more