Package com.okta.sdk.resource.model

Class RegistrationResponseCommandsInner

java.lang.Object
com.okta.sdk.resource.model.RegistrationResponseCommandsInner
All Implemented Interfaces:
Serializable
@Generated(value="org.openapitools.codegen.languages.JavaClientCodegen", date="2024-09-23T16:19:57.008753975Z[Etc/UTC]", comments="Generator version: 7.8.0") public class RegistrationResponseCommandsInner extends Object implements Serializable
RegistrationResponseCommandsInner
See Also:

  • Field Details

  • Constructor Details

    • RegistrationResponseCommandsInner

      public RegistrationResponseCommandsInner()

  • Method Details

    • type

      public RegistrationResponseCommandsInner type(String type)

    • getType

      @Nullable public String getType()
      The location where you specify the command. To set attributes in the user's Okta profile, supply a `type` property set to `com.okta.user.profile.update`, together with a `value` property set to a list of key-value pairs corresponding to the Okta user profile attributes you want to set. The attributes must already exist in your user profile schema. To explicitly allow or deny registration to the user, supply a type property set to `com.okta.action.update`, together with a value property set to `{\"registration\": \"ALLOW\"}` or `{\"registration\": \"DENY\"}`. The default is to allow registration. In Okta Identity Engine, to set attributes in the user's profile, supply a `type` property set to `com.okta.user.progressive.profile.update`, together with a `value` property set to a list of key-value pairs corresponding to the Progressive Enrollment attributes that you want to set. See [Registration inline hook - Send response](https://developer.okta.com/docs/guides/registration-inline-hook/nodejs/main/#send-response). Commands are applied in the order that they appear in the array. Within a single `com.okta.user.profile.update` or `com.okta.user.progressive.profile.update command`, attributes are updated in the order that they appear in the `value` object. You can never use a command to update the user's password, but you are allowed to set the values of attributes other than password that are designated sensitive in your Okta user schema. However, the values of those sensitive attributes, if included as fields in the Profile Enrollment form, aren't included in the `data.userProfile` object sent to your external service by Okta. See [data.userProfile](/openapi/okta-management/management/tag/InlineHook/#tag/InlineHook/operation/create-registration-hook!path=0/data/userProfile&t=request).
      Returns:
      type

    • setType

      public void setType(String type)

    • value

      public RegistrationResponseCommandsInner value(Map<String,Object> value)

    • putvalueItem

      public RegistrationResponseCommandsInner putvalueItem(String key, Object valueItem)

    • getValue

      @Nullable public Map<String,Object> getValue()
      The `value` object is the parameter to pass to the command. For `com.okta.user.profile.update` commands, `value` should be an object containing one or more name-value pairs for the attributes you wish to update. For `com.okta.action.update` commands, the value should be an object containing the attribute `action` set to a value of either `ALLOW` or `DENY`, indicating whether the registration should be permitted or not. Registrations are allowed by default, so setting a value of `ALLOW` for the action field is valid but superfluous.
      Returns:
      value

    • setValue

      public void setValue(Map<String,Object> value)

    • equals

      public boolean equals(Object o)
      Overrides:
      equals in class Object

    • hashCode

      public int hashCode()
      Overrides:
      hashCode in class Object

    • toString

      public String toString()
      Overrides:
      toString in class Object