com.amazonaws.services.identitymanagement.model.GetUserResult Maven / Gradle / Ivy
Show all versions of aws-java-sdk-iam Show documentation
/*
* Copyright 2020-2025 Amazon.com, Inc. or its affiliates. All Rights Reserved.
*
* Licensed under the Apache License, Version 2.0 (the "License"). You may not use this file except in compliance with
* the License. A copy of the License is located at
*
* http://aws.amazon.com/apache2.0
*
* or in the "license" file accompanying this file. This file is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
* CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions
* and limitations under the License.
*/
package com.amazonaws.services.identitymanagement.model;
import java.io.Serializable;
import javax.annotation.Generated;
/**
*
* Contains the response to a successful GetUser request.
*
*
* @see AWS API Documentation
*/
@Generated("com.amazonaws:aws-java-sdk-code-generator")
public class GetUserResult extends com.amazonaws.AmazonWebServiceResult implements Serializable, Cloneable {
/**
*
* A structure containing details about the IAM user.
*
*
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT to May
* 23, 2018 14:08 PDT. This affects last sign-in dates
* shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last used
* date that is returned is the date the user last signed in before May 3, 2018. For users that signed in after May
* 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you might
* delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we recommend
* that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if your users use
* access keys to access Amazon Web Services programmatically you can refer to access key last used information
* because it is accurate for all dates.
*
*
*/
private User user;
/**
*
* A structure containing details about the IAM user.
*
*
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT to May
* 23, 2018 14:08 PDT. This affects last sign-in dates
* shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last used
* date that is returned is the date the user last signed in before May 3, 2018. For users that signed in after May
* 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you might
* delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we recommend
* that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if your users use
* access keys to access Amazon Web Services programmatically you can refer to access key last used information
* because it is accurate for all dates.
*
*
*
* @param user
* A structure containing details about the IAM user.
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT
* to May 23, 2018 14:08 PDT. This affects last
* sign-in dates shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last
* used date that is returned is the date the user last signed in before May 3, 2018. For users that signed
* in after May 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you
* might delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we
* recommend that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if
* your users use access keys to access Amazon Web Services programmatically you can refer to access key last
* used information because it is accurate for all dates.
*
*/
public void setUser(User user) {
this.user = user;
}
/**
*
* A structure containing details about the IAM user.
*
*
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT to May
* 23, 2018 14:08 PDT. This affects last sign-in dates
* shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last used
* date that is returned is the date the user last signed in before May 3, 2018. For users that signed in after May
* 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you might
* delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we recommend
* that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if your users use
* access keys to access Amazon Web Services programmatically you can refer to access key last used information
* because it is accurate for all dates.
*
*
*
* @return A structure containing details about the IAM user.
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT
* to May 23, 2018 14:08 PDT. This affects last
* sign-in dates shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password
* last used date that is returned is the date the user last signed in before May 3, 2018. For users that
* signed in after May 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you
* might delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we
* recommend that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if
* your users use access keys to access Amazon Web Services programmatically you can refer to access key
* last used information because it is accurate for all dates.
*
*/
public User getUser() {
return this.user;
}
/**
*
* A structure containing details about the IAM user.
*
*
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT to May
* 23, 2018 14:08 PDT. This affects last sign-in dates
* shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last used
* date that is returned is the date the user last signed in before May 3, 2018. For users that signed in after May
* 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you might
* delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we recommend
* that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if your users use
* access keys to access Amazon Web Services programmatically you can refer to access key last used information
* because it is accurate for all dates.
*
*
*
* @param user
* A structure containing details about the IAM user.
*
* Due to a service issue, password last used data does not include password use from May 3, 2018 22:50 PDT
* to May 23, 2018 14:08 PDT. This affects last
* sign-in dates shown in the IAM console and password last used dates in the IAM credential
* report, and returned by this operation. If users signed in during the affected time, the password last
* used date that is returned is the date the user last signed in before May 3, 2018. For users that signed
* in after May 23, 2018 14:08 PDT, the returned password last used date is accurate.
*
*
* You can use password last used information to identify unused credentials for deletion. For example, you
* might delete users who did not sign in to Amazon Web Services in the last 90 days. In cases like this, we
* recommend that you adjust your evaluation window to include dates after May 23, 2018. Alternatively, if
* your users use access keys to access Amazon Web Services programmatically you can refer to access key last
* used information because it is accurate for all dates.
*
* @return Returns a reference to this object so that method calls can be chained together.
*/
public GetUserResult withUser(User user) {
setUser(user);
return this;
}
/**
* Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be
* redacted from this string using a placeholder value.
*
* @return A string representation of this object.
*
* @see java.lang.Object#toString()
*/
@Override
public String toString() {
StringBuilder sb = new StringBuilder();
sb.append("{");
if (getUser() != null)
sb.append("User: ").append(getUser());
sb.append("}");
return sb.toString();
}
@Override
public boolean equals(Object obj) {
if (this == obj)
return true;
if (obj == null)
return false;
if (obj instanceof GetUserResult == false)
return false;
GetUserResult other = (GetUserResult) obj;
if (other.getUser() == null ^ this.getUser() == null)
return false;
if (other.getUser() != null && other.getUser().equals(this.getUser()) == false)
return false;
return true;
}
@Override
public int hashCode() {
final int prime = 31;
int hashCode = 1;
hashCode = prime * hashCode + ((getUser() == null) ? 0 : getUser().hashCode());
return hashCode;
}
@Override
public GetUserResult clone() {
try {
return (GetUserResult) super.clone();
} catch (CloneNotSupportedException e) {
throw new IllegalStateException("Got a CloneNotSupportedException from Object.clone() " + "even though we're Cloneable!", e);
}
}
}