Skip to main content

OATH Authentication


OATH Authentication


Giving access to sensitive information with the users permission.

There are usually 4 parties involved in this process.

  • The User, 'The User'.
  • The Application requesting access to the User's data, 'The Requesting Application'.
  • The Application which has the User's data, 'The User's Data Host'.
  • The Application which can grant access to the User's data, 'The Access App'.


(A token is just a piece of unique text which the receiver reads and understands and can identify and grant permission to access some data or resource).

There are more than 1 steps involved:

  1. 'The Requesting Application' requests access to 'The User's data.
  2. 'The Requesting Application's request is sent to 'The Access App'.
  3. 'The Access App' asks 'The User' if she wishes to grant permission to 'The Requesting Application'.
  4. 'The User' agrees and response is sent to 'The Access App'.
  5. 'The Access App' responds to 'The Requesting Application' granting permission.
  6. 'The Access App' sends a Token to 'The Requesting Application'.
  7. 'The Requesting Application' now sends requests to 'The User's Data Host' and attaches the Token to the request.
  8. 'The User's Data Host' responds to 'The Requesting Application' with the data.




https://www.youtube.com/watch?v=CPbvxxslDTU


Labels:

Comments

Post a Comment

Popular posts from this blog

dotNET - Debugging

Debugging with .NET MSIL assemblies Visual Studio and debugging the CLR are different, I'll talk about both. MSIL Assemblies Assemblies compiled with .NET tools such as the CLR compiler are compiled into a file which contains MSIL (Microsoft Intermediate Language). At runtime the contents of the assembly are loaded into the CLR and ran as machine code. When you compile an assembly in debug a PDB file is generated alongside the DLL or EXE you've just created. The link between these 2 files is that the PDB contains the line numbers of the methods and classes as well as the file names of the original source code that created the assembly. When you launch the debugger in Visual Studio the assembly is loaded into the Debugger (similar to the CLR) along with the PDB file. The debugger now uses your PDB file contents to match the running code found in the assembly to locations in source files (hopefully in your present project). CLR CLR Inside Out (msdn magazine) .NET Framework Tools:...
7 comments
Read more

Installer CustomAction, Debugging the CustomAction, InstallState

Custom Action The Custom Action is added to the Setup Project, select the Project node and hit the Custom Action button. This allows you add an Action to a particular phase in the Installation. But first you must create the Custom Action. To Add a Custom Action you must first have a Custom Action created, this is usually in the form of a Installer Class, this should be created in a seperate project, the Installer Class is actually one of the File Templates in the C# Projects. So it's File->New Project and select Visual C# Projects. Then add a Class Library, this will prompt you for the Class Library Types , select "Installer Class". Walkthrough - Creating Custom Action (msdn). Also here's a more comprehensive document on Setup/Installer implementations, it delves into the Registry etc Getting Started with Setup Projects (SimpleTalk). Visual Studio Setup Projects and Custom Actions (Simple Talk). Create your Installer Class and then add it as a Custom Action to the ...
3 comments
Read more

dotNET - Use app.config ApplicationSettings and UserSettings

When using Settings in an Assembly or .exe you can use the Settings Designer to generate a config file using Settings. The Settings Designer provides a wrapper class which allows you to provide defaults and access the config data using Properties. But what if you're not working inside that Assembly or .exe? this presents a problem. If your loading the Assembly externally and want to access that Assembly's .config file you'll probably wish to use something in the System.Configuration namespace... unfortunately it's not of much use if you've created the .config file from the Settings Designer in Visual Studio!! This is because the Designer creates Sections and ApplicationSettings and UserSettings, the System.Configuration namespace does not provide a method to access these (it has a method to access AppSettings which are a different thing. Below I've written a workaround which locates the app.config and accesses the ApplicationSettings and UserSettings using XML i...
8 comments
Read more