3

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

var param =
{
    IdentityPoolId: "us-east-1:the-full-identity-id",
    Logins: {} // To have provider name in a variable
};
param.Logins["com.test.website.login"] = userIdICreatedAndStoredInDynamoDB;

cognitoidentity.getOpenIdTokenForDeveloperIdentity(param,
function(err, data)
{
    if (err) return fn(err); // an error occurred
    else fn(null, data.IdentityId, data.Token); // successful response
});

它返回该用户的身份标识和令牌。一切都使用 IAM 角色和 AWS Cognito Identity 进行设置,并且似乎正在控制台中进行身份验证。

我有两个问题:

  1. 如何在应用程序中测试用户是否已通过身份验证?我将身份标识和令牌保存在应用设备中。
  2. 身份验证持续多长时间?我希望用户保持登录状态。这就是我使用的大多数应用程序的工作方式并保持登录状态,直到他们退出。

谢谢。

4

2 回答 2

7

回答第一个问题:

如何在应用程序中测试用户是否已通过身份验证?我将identityIdand 令牌保存在应用程序设备中。

您通过制作“自定义授权人”来测试身份验证

当您创建一个新函数时,您可以在 Lambda 示例函数中找到 AWS 示例函数 (如果您过滤到 NodeJS 4.3 函数,则它朝向后面)

或者你可以在 GitHub 上查看THIS ,这是相同的东西。

我在这里做了一个修改版本:

"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. 将您的PoolIdandprincipalId放入环境变量中,以便以后更改
  3. 前往 API Gateway 并将其链接起来
  4. 在左侧的 API 选项下,点击Authorizers
  5. 点击Create->Custom Authorizer
  6. 填写您的 Lambda 区域、函数名称(应自动填写)、授权人名称、身份令牌来源(暂时保持简单method.request.header.Authorization,TTL 可以为 300。我们先不要弄乱执行角色或令牌验证表达式。
  7. 保存/更新它并返回 Lambda - 我们稍后将与此授权人连接一个函数。

好的,所以当您查看我的函数时,您会发现我在最顶部执行了这个奇怪的加密/解密操作:

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;
    }
};

基本上,我将一些我想要的项目包装在一个加密的密钥中,这样我就可以将我的所有信息传递给 easy-peasy。(我将身份池作为哈希传递,以使其既酷又简单,只要您从不将身份池 ID 发送到前端,我们就很好!)

自定义授权者需要一个令牌,而不是您所说的“令牌”或其他东西的 JSON 块(您可以这样做,但看起来很愚蠢)

所以我们有一个统一的令牌被传入,我调用这个decrypt函数来解包(我将在一秒钟内展示加密示例。

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

好的,既然您看到了该部分,请向下查看函数的底部。

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 Gateway 传入的数据是:

{
    "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存在并且它是 a string,如果不是,我们说它是Unauthorized(每个人都应该知道并使用他们的状态代码)

其次,我解密令牌并确保try-catch尝试顺利进行。如果进展不顺利,他们将Unauthorized. 如果是这样,我们可以Continue

你会在令牌中看到,我放了一个变量Expiration,这就是我检查密钥是否曾经被接受并且正确并且现在只是过期的方式。为此,我说Proxy Authentication Required。这告诉我的前端,再次调用登录并给我新的信誉。别忘了,这个函数的目的只能是检查我们是否被授权。不要做刷新令牌之类的花哨的事情。

接下来,我检查一切是否正常,然后调用denyAllMethods并将响应代码放入context响应中。API Gateway 非常挑剔,只希望传递简单的 IAM 格式策略 -如果未在此处此处指定,则没有其他信息或格式或任何可能存在的内容

如果一切正常,我调用getCredentialsForIdentity- 使用IdentityIdand Token,确保令牌实际上也是有效的,然后我允许当时需要的功能。这些非常重要,并且将仅验证这些功能的令牌- 换句话说。如果您在 IAM 中的 IAM 角色说它可以访问所有内容,这将拒绝,您只能访问GETon/userDELETEon /user。所以不要让它愚弄你。毕竟这是一个自定义授权者。

接下来,我需要向您展示我是如何从登录部分输入所有这些内容的。我有相同的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

部分。

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

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

您创建一个OpenIdToken使用他们的电子邮件或任何您想识别他们的东西,并TokenDuration几秒钟内完成。我建议一两个星期做这个,但如果你想要一年之类的,31536000就可以了。另一种方法是创建一个只为您提供授权凭据的函数,而不是denyAll在出现407场景时调用授权者,而是创建他们可以调用的唯一方法allowMethod( POST, /updateCreds );或类似的方法。这样你就可以不时刷新他们的东西。

伪的是:

消除:

if( response.statusCode >= 400 )
else

并做:

if( statusCode >= 400 )
    denyAll
else if( statusCode === 407 )
    allow refresh function
else
    allow everything else

希望这可以帮助!

于 2017-01-02T13:01:05.857 回答
0

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

您的 Cognito 令牌只能使用一个小时,但您可以刷新令牌以保持用户登录。当您的用户进行身份验证时,他们获得了三个令牌:ID、访问和刷新令牌。您可以使用后者来请求新的访问令牌。

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

于 2016-12-30T14:16:10.083 回答