Implicit grants are now sort of working on the authorization server side.

Still to do:
 * Ensure no auto-authorize of access tokens based on previous authorizations for the unauthenticated client.
 * Provide the authorization server with a way to indicate access token lifetime, and to veto the request based on the requested scopes being too dangerous for the less secure implicit grant type.

1 files changed, 41 insertions, 9 deletions

diff --git a/samples/OAuthAuthorizationServer/Code/OAuth2AuthorizationServer.cs b/samples/OAuthAuthorizationServer/Code/OAuth2AuthorizationServer.cs
index e2e4325..07cdd9d 100644
--- a/samples/OAuthAuthorizationServer/Code/OAuth2AuthorizationServer.cs
+++ b/samples/OAuthAuthorizationServer/Code/OAuth2AuthorizationServer.cs
@@ -11,7 +11,25 @@
 	using DotNetOpenAuth.OAuth2.Messages;
 
 	internal class OAuth2AuthorizationServer : IAuthorizationServer {
-		private static readonly RSAParameters AsymmetricTokenSigningPrivateKey = CreateRSAKey();
+		private static readonly RSACryptoServiceProvider AsymmetricTokenSigningPrivateKey = CreateRSA();
+
+#if SAMPLESONLY
+		/// <summary>
+		/// This is the FOR SAMPLE ONLY hard-coded public key of the complementary OAuthResourceServer sample.
+		/// </summary>
+		/// <remarks>
+		/// In a real app, the authorization server would need to determine which resource server the access token needs to be encoded for
+		/// based on the authorization request.  It would then need to look up the public key for that resource server and use that in 
+		/// preparing the access token for the client to use against that resource server.
+		/// </remarks>
+		private static readonly RSAParameters ResourceServerEncryptionPublicKey = new RSAParameters {
+			Exponent = new byte[] { 1, 0, 1 },
+			Modulus = new byte[] { 166, 175, 117, 169, 211, 251, 45, 215, 55, 53, 202, 65, 153, 155, 92, 219, 235, 243, 61, 170, 101, 250, 221, 214, 239, 175, 238, 175, 239, 20, 144, 72, 227, 221, 4, 219, 32, 225, 101, 96, 18, 33, 117, 176, 110, 123, 109, 23, 29, 85, 93, 50, 129, 163, 113, 57, 122, 212, 141, 145, 17, 31, 67, 165, 181, 91, 117, 23, 138, 251, 198, 132, 188, 213, 10, 157, 116, 229, 48, 168, 8, 127, 28, 156, 239, 124, 117, 36, 232, 100, 222, 23, 52, 186, 239, 5, 63, 207, 185, 16, 137, 73, 137, 147, 252, 71, 9, 239, 113, 27, 88, 255, 91, 56, 192, 142, 210, 21, 34, 81, 204, 239, 57, 60, 140, 249, 15, 101 },
+		};
+#else
+		[Obsolete("You must use a real key for a real app.", true)]
+		private static readonly RSAParameters ResourceServerEncryptionPublicKey;
+#endif
 
 		#region Implementation of IAuthorizationServer
 
@@ -23,9 +41,17 @@
 			get { return MvcApplication.KeyNonceStore; }
 		}
 
-		public RSACryptoServiceProvider CreateAccessTokenSigningCryptoServiceProvider() {
+		public RSACryptoServiceProvider AccessTokenSigningKey {
+			get { return AsymmetricTokenSigningPrivateKey; }
+		}
+
+		public RSACryptoServiceProvider CreateAccessTokenEncryptionKey(IAccessTokenRequest accessTokenRequestMessage) {
 			var asymmetricTokenSigningServiceProvider = new RSACryptoServiceProvider();
-			asymmetricTokenSigningServiceProvider.ImportParameters(AsymmetricTokenSigningPrivateKey);
+
+			// For this sample, we assume just one resource server.
+			// If this authorization server needs to mint access tokens for more than one resource server,
+			// we'd look at the request message passed to us and decide which public key to return.
+			asymmetricTokenSigningServiceProvider.ImportParameters(ResourceServerEncryptionPublicKey);
 			return asymmetricTokenSigningServiceProvider;
 		}
 
@@ -107,18 +133,24 @@
 #endif
 		}
 
+		private static RSACryptoServiceProvider CreateRSA() {
+			var rsa = new RSACryptoServiceProvider();
+			rsa.ImportParameters(CreateRSAKey());
+			return rsa;
+		}
+
 		private bool IsAuthorizationValid(HashSet<string> requestedScopes, string clientIdentifier, DateTime issuedUtc, string username) {
 			// If db precision exceeds token time precision (which is common), the following query would
 			// often disregard a token that is minted immediately after the authorization record is stored in the db.
 			// To compensate for this, we'll increase the timestamp on the token's issue date by 1 second.
 			issuedUtc += TimeSpan.FromSeconds(1);
 			var grantedScopeStrings = from auth in MvcApplication.DataContext.ClientAuthorizations
-			                          where
-			                              auth.Client.ClientIdentifier == clientIdentifier &&
-			                              auth.CreatedOnUtc <= issuedUtc &&
-			                              (!auth.ExpirationDateUtc.HasValue || auth.ExpirationDateUtc.Value >= DateTime.UtcNow) &&
-			                              auth.User.OpenIDClaimedIdentifier == username
-			                          select auth.Scope;
+									  where
+										  auth.Client.ClientIdentifier == clientIdentifier &&
+										  auth.CreatedOnUtc <= issuedUtc &&
+										  (!auth.ExpirationDateUtc.HasValue || auth.ExpirationDateUtc.Value >= DateTime.UtcNow) &&
+										  auth.User.OpenIDClaimedIdentifier == username
+									  select auth.Scope;
 
 			if (!grantedScopeStrings.Any()) {
 				// No granted authorizations prior to the issuance of this token, so it must have been revoked.