GAE Cloud Endpoint未显示401 auth错误

时间:2015-02-08 06:21:46

标签: google-app-engine google-cloud-endpoints

我正在尝试使用身份验证来保存配置文件,但即使用户为空,GAE Endpoint也不会给出401错误。

相反,Endpoint响应200 ok并给出默认结果。

BTW这是Udacity Course的一部分。

/**
 * Creates or updates a Profile object associated with the given user
 * object.
 *
 * @param user
 *            A User object injected by the cloud endpoints.
 * @param profileForm
 *            A ProfileForm object sent from the client form.
 * @return Profile object just created.
 * @throws UnauthorizedException
 *             when the User object is null.
 */

// Declare this method as a method available externally through Endpoints
@ApiMethod(name = "saveProfile", path = "profile", httpMethod = HttpMethod.POST)
// The request that invokes this method should provide data that
// conforms to the fields defined in ProfileForm

// TODO 1 Pass the ProfileForm parameter
// TODO 2 Pass the User parameter
public Profile saveProfile(final User user) throws UnauthorizedException {

    String userId = null;
    String mainEmail = null;
    String displayName = "Your name will go here";
    TeeShirtSize teeShirtSize = TeeShirtSize.NOT_SPECIFIED;

    // TODO 2
    // If the user is not logged in, throw an UnauthorizedException
    if(user== null){
        throw new UnauthorizedException("Authorization Required!");
    }
    // TODO 1
    // Set the teeShirtSize to the value sent by the ProfileForm, if sent
    // otherwise leave it as the default value

    // TODO 1
    // Set the displayName to the value sent by the ProfileForm, if sent
    // otherwise set it to null

    // TODO 2
    // Get the userId and mainEmail

    // TODO 2
    // If the displayName is null, set it to default value based on the user's email
    // by calling extractDefaultDisplayNameFromEmail(...)

    // Create a new Profile entity from the
    // userId, displayName, mainEmail and teeShirtSize
    Profile profile = new Profile(userId, displayName, mainEmail, teeShirtSize);

    // TODO 3 (In Lesson 3)
    // Save the Profile entity in the datastore

    // Return the profile
    return profile;
}

1 个答案:

答案 0 :(得分:0)

不幸的是它是known issue。转到"Star" this issue以获取有关何时修复的更新。第一个链接中有几个解决方法,下面引用它:

  

有两种解决方法(1)保存用户并从中读回   store,如果它引用了有效帐户,则将填充用户ID   (这很糟糕,因为你支付了保存/加载/删除费用   即使它很小,每个API访问都经过身份验证,并且   显然有一些性能成本)和(2)你可以使用谷歌+ ID   但这与用户ID不同。