Skip to content

Unable to set or modify an sub-org's email "From" address #25959

@sanjulamadurapperuma

Description

@sanjulamadurapperuma

Description

In order to set or modify an organization's email "From" address in WSO2 Identity Server v7.1.0, assume the V1 Notification sender APIs are used (which are utilized to create or modify a Notification sender) [1] [2].

From WSO2 Identity Server v7.1.0 update level 22, these APIs fail with a 400 HTTP error code with the error message "Invalid input received for notification sender".

Utilizing the following payload will resolve the error, but it needs to be fixed as it has stopped working without a proper update of the documentation or the update changelog.

{
  "smtpServerHost": "smtp.gmail.com",
  "smtpPort": 587,
  "fromAddress": "***",
  "userName": "***",
  "password": "***",
  "properties": [
    {
      "mail.smtp.signature": "Display Name",
      "mail.smtp.replyTo": "<mail>",
      "key": "mail.smtp.starttls.enable",
      "value": true
    }
  ]
}

[1] - https://is.docs.wso2.com/en/latest/apis/notification-sender-rest-api/#tag/Email-Senders/operation/createEmailSender%29
[2] - https://is.docs.wso2.com/en/latest/apis/notification-sender-rest-api/#tag/Email-Senders/operation/updateEmailSender%29

Steps to Reproduce

  • Set up a WSO2 IS v7.1.0.22 instance.
  • Invoke the Notification Sender REST API to update the senders for a sub-org as mentioned in [1] [2].
  • Notice the error returned.

Please select the area issue is related to

Other

Version

v7.1.0

Environment Details (with versions)

No response

Developer Checklist

  • [Behavioural Change] Does this change introduce a behavioral change to the product?
  •  ↳ Approved by team lead
  •  ↳ Label impact/behavioral-change added
  • [Migration Impact] Does this change have a migration impact?
  •  ↳ Migration label added (e.g., 7.2.0-migration)
  •  ↳ Migration issues created and linked
  • [New Configuration] Does this change introduce a new configuration?
  •  ↳ Label config added
  •  ↳ Configuration is properly documented

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions