使用AWS IOS SDK验证用户是否已通过身份验证

时间:2016-12-30 08:37:48

标签: ios objective-c amazon-web-services amazon-cognito aws-cognito

我创建了一个lamdba函数,它执行以下操作:

<tl-no-tag></tl-no-tag>

它返回该用户的identityId和token。所有内容都使用IAM角色和AWS Cognito Identity进行设置,并且似乎在控制台中进行身份验证。

我有两个问题:

  1. 如何在应用中测试用户是否经过身份验证?我在应用设备中保存了identityId和令牌。
  2. 身份验证持续多长时间?我希望用户保持登录状态。这就是我使用的大多数应用程序的工作方式,并且在他们注销之前一直保持登录状态。
  3. 感谢。

2 个答案:

答案 0 :(得分:6)

回答第一个问题:

  

如何在应用中测试用户是否经过身份验证?我在应用设备中保存了identityId和令牌。

您可以通过制作&#34;自定义授权程序&#34;

来测试身份验证

当您创建新函数时,您可以在Lambda示例函数中找到AWS示例函数 (如果您过滤到NodeJS 4.3功能,它会向后移动)

或者你可以看看THIS这是同一件事,只是在GitHub上。

我在这里修改了 sorta 版本:

"use strict";

const
    codes  = {
        100: "Continue", 101: "Switching Protocols", 102: "Processing",
        200: "OK", 201: "Created", 202: "Accepted", 203: "Non-Authoritative Information", 204: "No Content", 205: "Reset Content", 206: "Partial Content", 207: "Multi-Status", 208: "Already Reported", 226: "IM Used",
        300: "Multiple Choices", 301: "Moved Permanently", 302: "Found", 303: "See Other", 304: "Not Modified", 305: "Use Proxy", 307: "Temporary Redirect", 308: "Permanent Redirect",
        400: "Bad Request", 401: "Unauthorized", 402: "Payment Required", 403: "Forbidden", 404: "Not Found", 405: "Method Not Allowed", 406: "Not Acceptable", 407: "Proxy Authentication Required", 408: "Request Timeout", 409: "Conflict", 410: "Gone", 411: "Length Required", 412: "Precondition Failed", 413: "Payload Too Large", 414: "URI Too Long",
        415: "Unsupported Media Type", 416: "Range Not Satisfiable", 417: "Expectation Failed", 418: "I'm a teapot", 421: "Misdirected Request", 422: "Unprocessable Entity", 423: "Locked", 424: "Failed Dependency", 425: "Unordered Collection", 426: "Upgrade Required", 428: "Precondition Required", 429: "Too Many Requests", 431: "Request Header Fields Too Large", 451: "Unavailable For Legal Reasons",
        500: "Internal Server Error", 501: "Not Implemented", 502: "Bad Gateway", 503: "Service Unavailable", 504: "Gateway Timeout", 505: "HTTP Version Not Supported", 506: "Variant Also Negotiates", 507: "Insufficient Storage", 508: "Loop Detected", 509: "Bandwidth Limit Exceeded", 510: "Not Extended", 511: "Network Authentication Required"
    },
    resp   = ( statusCode, data ) => ( { statusCode, message: codes[ statusCode ], data } ),
    AWS    = require( "aws-sdk" ),
    crypto = require( "crypto" ),
    COG    = new AWS.CognitoIdentity(),
    token  = {
        algorithm: "aes-256-ctr",
        encrypt: item => {
            item = JSON.stringify( item );
            let cipher = crypto.createCipher( token.algorithm, process.env.PoolId ),
                crypted = cipher.update( item, 'utf8', 'base64' );
            crypted += cipher.final( 'base64' );
            return crypted;
        },
        decrypt: item => {
            let decipher = crypto.createDecipher( token.algorithm, process.env.PoolId ),
                dec = decipher.update( item, 'base64', 'utf8' );
            dec += decipher.final( 'utf8' );
            return dec;
        }
    };

function AuthPolicy( principal, awsAccountId, apiOptions ) {
    this.awsAccountId = awsAccountId;
    this.principalId = principal;
    this.version = '2012-10-17';
    this.pathRegex = new RegExp( '^[/.a-zA-Z0-9-\*]+$' );
    this.allowMethods = [];
    this.denyMethods = [];

    if( !apiOptions || !apiOptions.restApiId ) this.restApiId = '*';
    else this.restApiId = apiOptions.restApiId;

    if( !apiOptions || !apiOptions.region ) this.region = '*';
    else this.region = apiOptions.region;

    if( !apiOptions || !apiOptions.stage ) this.stage = '*';
    else this.stage = apiOptions.stage;
}

AuthPolicy.HttpVerb = {
    GET: 'GET',
    POST: 'POST',
    PUT: 'PUT',
    PATCH: 'PATCH',
    HEAD: 'HEAD',
    DELETE: 'DELETE',
    OPTIONS: 'OPTIONS',
    ALL: '*',
};

AuthPolicy.prototype = ( function AuthPolicyClass() {

    function addMethod( effect, verb, resource, conditions ) {
        if( verb !== '*' && !Object.prototype.hasOwnProperty.call( AuthPolicy.HttpVerb, verb ) ) {
            throw new Error( `Invalid HTTP verb ${verb}. Allowed verbs in AuthPolicy.HttpVerb` );
        }

        if( !this.pathRegex.test( resource ) )
            throw new Error( `Invalid resource path: ${resource}. Path should match ${this.pathRegex}` );

        let cleanedResource = resource;

        if( resource.substring( 0, 1 ) === '/' )
            cleanedResource = resource.substring( 1, resource.length );

        const resourceArn = `arn:aws:execute-api:${this.region}:${this.awsAccountId}:${this.restApiId}/${this.stage}/${verb}/${cleanedResource}`;

        if( effect.toLowerCase() === 'allow' )
            this.allowMethods.push( {
                resourceArn,
                conditions,
            } );
        else if( effect.toLowerCase() === 'deny' )
            this.denyMethods.push( {
                resourceArn,
                conditions,
            } );
    }

    function getEmptyStatement( effect ) {
        const statement = {};
        statement.Action = 'execute-api:Invoke';
        statement.Effect = effect.substring( 0, 1 ).toUpperCase() + effect.substring( 1, effect.length ).toLowerCase();
        statement.Resource = [];

        return statement;
    }

    function getStatementsForEffect( effect, methods ) {
        const statements = [];

        if( methods.length > 0 ) {
            const statement = getEmptyStatement( effect );

            for( let i = 0; i < methods.length; i++ ) {
                const curMethod = methods[ i ];
                if( curMethod.conditions === null || curMethod.conditions.length === 0 )
                    statement.Resource.push( curMethod.resourceArn );
                else {
                    const conditionalStatement = getEmptyStatement( effect );
                    conditionalStatement.Resource.push( curMethod.resourceArn );
                    conditionalStatement.Condition = curMethod.conditions;
                    statements.push( conditionalStatement );
                }
            }

            if( statement.Resource !== null && statement.Resource.length > 0 )
                statements.push( statement );
        }
        return statements;
    }

    return {
        constructor: AuthPolicy,
        allowAllMethods() {
            addMethod.call( this, 'allow', '*', '*', null );
        },
        denyAllMethods() {
            addMethod.call( this, 'deny', '*', '*', null );
        },
        allowMethod( verb, resource ) {
            addMethod.call( this, 'allow', verb, resource, null );
        },
        denyMethod( verb, resource ) {
            addMethod.call( this, 'deny', verb, resource, null );
        },
        allowMethodWithConditions( verb, resource, conditions ) {
            addMethod.call( this, 'allow', verb, resource, conditions );
        },
        denyMethodWithConditions( verb, resource, conditions ) {
            addMethod.call( this, 'deny', verb, resource, conditions );
        },
        build() {
            if( ( !this.allowMethods || this.allowMethods.length === 0 ) &&
                ( !this.denyMethods || this.denyMethods.length === 0 ) )
                throw new Error( 'No statements defined for the policy' );

            const policy = {}, doc = {};
            policy.principalId = this.principalId;

            doc.Version = this.version;
            doc.Statement = [];
            doc.Statement = doc.Statement.concat( getStatementsForEffect.call( this, 'Allow', this.allowMethods ) );
            doc.Statement = doc.Statement.concat( getStatementsForEffect.call( this, 'Deny', this.denyMethods ) );

            policy.policyDocument = doc;

            return policy;
        },
    };
} () );


exports.handler = ( event, context, cb ) => {
    const
        principalId      = process.env.principalId,
        tmp              = event.methodArn.split( ':' ),
        apiGatewayArnTmp = tmp[ 5 ].split( '/' ),
        awsAccountId     = tmp[ 4 ],
        apiOptions       = {
            region: tmp[ 3 ],
            restApiId: apiGatewayArnTmp[ 0 ],
            stage: apiGatewayArnTmp[ 1 ]
        },
        policy = new AuthPolicy( principalId, awsAccountId, apiOptions );

    let response;

    if( !event.authorizationToken || typeof event.authorizationToken !== "string" )
        response = resp( 401 );

    let item = token.decrypt( event.authorizationToken );

    try { item = resp( 100, JSON.parse( item ) ); }
    catch( e ) { item = resp( 401 ); }

    if( item.statusCode !== 100 )
        response = resp( 401 );
    else if( item.data.Expiration <= new Date().getTime() )
        response = resp( 407 );
    else
        response = resp( 100 );

    if( response.statusCode >= 400 ) {
        policy.denyAllMethods();
        const authResponse = policy.build();
        authResponse.context = response;
        cb( null, authResponse );
    } else {
        COG.getCredentialsForIdentity( {
            IdentityId: item.data.IdentityId,
            Logins: {
                'cognito-identity.amazonaws.com': item.data.Token
            }
        }, ( e, d ) => {
            if( e ) {
                policy.denyAllMethods();
                response = resp( 401 );
            } else {
                policy.allowMethod( AuthPolicy.HttpVerb.GET, "/user" );
                policy.allowMethod( AuthPolicy.HttpVerb.DELETE, "/user" );
                response = resp( 202 );
            }

            const authResponse = policy.build();
            authResponse.context = response;
            cb( null, authResponse );
        } );
    }
};

上面是完整的例子......但是让我分解一下并解释为什么他们提供的那个没有帮助。

以下是设置此步骤的步骤,以便您可以了解为什么必须这样。

  1. 转到Lambda并创建一个名为Auth_isValid的函数或类似的函数
  2. 将您的PoolIdprincipalId放入环境变量中,以便以后轻松更改
  3. 转到API网关,然后将其链接起来
  4. 在左侧的API选项下,点击Authorizers
  5. 点击Create - &gt; Custom Authorizer
  6. 填写您的Lambda区域,功能名称(应自动填充),授权者名称,身份令牌源(暂时保持简单method.request.header.Authorization,TTL可以是300.不要乱用执行角色或令牌验证表达式。
  7. 保存/更新它并返回Lambda - 稍后我们将与此授权程序挂钩。
  8. 好的,当你看看我的功能时,你会发现我在最顶层做了这个奇怪的加密/解密事情:

    token  = {
        algorithm: "aes-256-ctr",
        encrypt: item => {
            item = JSON.stringify( item );
            let cipher = crypto.createCipher( token.algorithm, process.env.PoolId ),
                crypted = cipher.update( item, 'utf8', 'base64' );
            crypted += cipher.final( 'base64' );
            return crypted;
        },
        decrypt: item => {
            let decipher = crypto.createDecipher( token.algorithm, process.env.PoolId ),
                dec = decipher.update( item, 'base64', 'utf8' );
            dec += decipher.final( 'utf8' );
            return dec;
        }
    };
    

    基本上,我将一些我想要的项目包装在一个简单的加密密钥中,这样我就可以轻松地将所有信息传递给我。 (我将身份池作为哈希传递,使其变得简单明了,只要你永远不会将身份池ID发送到前端,我们就会很好!)

    自定义授权程序需要一个令牌,而不是您所说的是一个&#34;令牌&#34;的JSON块。或某事(你可以做但看起来很愚蠢)

    因此,我们有一个传入的统一令牌,我调用decrypt函数进行解包(我将在一秒钟内显示加密示例。

    现在有些人可能会说&#34;哦,实际上并不是加密它很容易被弄清楚&#34; - 我对此的回答是:&#34;你好,它本来是未加密的,原始文本无论如何,为什么不让它变得容易。&#34;

    现在好了,你看到那个部分,一直到功能的底部。

    let response;
    
    if( !event.authorizationToken || typeof event.authorizationToken !== "string" )
        response = resp( 401 );
    
    let item = token.decrypt( event.authorizationToken );
    
    try { item = resp( 100, JSON.parse( item ) ); }
    catch( e ) { item = resp( 401 ); }
    
    if( item.statusCode !== 100 )
        response = resp( 401 );
    else if( item.data.Expiration <= new Date().getTime() )
        response = resp( 407 );
    else
        response = resp( 100 );
    
    if( response.statusCode >= 400 ) {
        policy.denyAllMethods();
        const authResponse = policy.build();
        authResponse.context = response;
        cb( null, authResponse );
    } else {
        COG.getCredentialsForIdentity( {
            IdentityId: item.data.IdentityId,
            Logins: {
                'cognito-identity.amazonaws.com': item.data.Token
            }
        }, ( e, d ) => {
            if( e ) {
                policy.denyAllMethods();
                response = resp( 401 );
            } else {
                policy.allowMethod( AuthPolicy.HttpVerb.GET, "/user" );
                policy.allowMethod( AuthPolicy.HttpVerb.DELETE, "/user" );
                response = resp( 202 );
            }
    
            const authResponse = policy.build();
            authResponse.context = response;
            cb( null, authResponse );
        } );
    }
    

    <强>更新

      

    我们从API网关传入的数据是:

    {
        "type":"TOKEN",
        "authorizationToken":"<session_token>",
        "methodArn":"arn:aws:execute-api:<region>:<Account_ID>:<API_ID>/<Stage>/<Method>/<Resource_Path>"
    }
    
      

    我们来自Lambda的传出数据应该是这样的:

    {
        "Version": "2012-10-17",
        "Statement": [
            {
                "Action": "execute-api:Invoke",
                "Effect": "Deny",
                "Resource": [
                    "arn:aws:execute-api:<region>:<Account_ID>:<API_ID>/<Stage>/*/*"
                ]
            }
        ]
    }
    
      

    取决于我们的授权方式。


    因此,在我的第一次if检查中,我确保authorizationToken在那里并且它是string,如果不是,我们会说#&} 39; s Unauthorized(每个人都应该知道并使用他们的状态代码)

    其次,我解密了令牌,并确保在尝试try-catch时表现良好。如果它没有顺利,他们会Unauthorized。如果确实如此,我们可以Continue

    您将在令牌中看到我放置一个变量Expiration,这就是我检查密钥是否曾被接受并且正确并且现在只是过期的方式。为此,我说Proxy Authentication Required。这告诉了我的前端,再次登录并给我新的信誉。不要忘记,此功能的目的只是检查我们是否经过授权。不要做像刷新令牌这样的奇特事情。

    接下来,我检查一切是否正常并致电denyAllMethods并将响应代码放入响应的context。 API网关非常挑剔,只想简单地传递IAM格式的政策 - 没有其他信息或格式,或者如果没有指定HEREHERE

    如果一切正常,我拨打getCredentialsForIdentity - 使用IdentityIdToken,确保该令牌实际上也是有效的,然后我允许所需的功能时间。这些非常重要,只会将令牌验证为那些功能 - 换句话说。如果您在IAM中的IAM角色说它可以访问所有内容,则会拒绝,您只能访问GET上的/userDELETE上的/user。所以不要让它欺骗你。毕竟,这是自定义授权程序

    接下来,我需要向您展示如何将所有这些放入Login部分。我有相同的token = {部分,但在我的登录功能中,我添加了getToken函数:

    token.getToken = obj => {
        return new Promise( ( res, rej ) => {
            COG.getOpenIdTokenForDeveloperIdentity( {
                IdentityPoolId: process.env.PoolId,
                Logins: {
                    "com.whatever.developerIdthing": obj.email
                },
                TokenDuration: duration
            }, ( e, r ) => {
                r.Expiration = new Date().getTime() + ( duration * 1000 );
                if( e ) rej( e );
                else res( token.encrypt( r ) );
            } );
        } );
    };
    

    请注意上面的:

    duration

    部分

    这是你第二个问题的答案:

      

    身份验证持续多长时间?我希望用户保持登录状态。这就是我使用的大多数应用程序的工作方式,并且在他们注销之前一直保持登录状态。

    您使用他们的电子邮件或任何您想要识别的电子邮件创建OpenIdTokenTokenDuration处于。我建议一两个星期,但如果你想要一年或者其他什么,31536000就是这样。另一种方法是创建一个只提供授权凭据的函数,而不是在denyAll场景出现时调用授权器中的407,而是创建他们可以调用的唯一方法{{1 }} 或类似的东西。这样你就可以每隔一段时间刷新一次。

    伪的是:

    卸下:

    allowMethod( POST, /updateCreds );

    并做:

    if( response.statusCode >= 400 )
    else
    

    希望这有帮助!

答案 1 :(得分:0)

要测试他们是否已登录,您需要设置一项服务,以便针对Cognito检查令牌。快速而肮脏的方法是设置一个基本的lambda,通过API Gateway使用指向您的用户身份池的授权程序公开它。所有lambda需要做的是返回HTTP 200,因为你真正检查的是授权者。然后让你的应用程序获取/发布/等到具有“授权”标题的API API:$ ACCESS_TOKEN。无论是成功还是反击200还是会返回未经授权的消息。

您的Cognito令牌仅适用于一小时,但您可以刷新令牌以保持用户登录。当您的用户通过身份验证时,他们会获得三个令牌:ID,访问和刷新令牌。您可以使用后者请求新的访问令牌。

记录于:http://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-user-pools-using-tokens-with-identity-providers.html