Facing issue on Remote Event Receiver SharePoint online after updating clientID and clientSecret

Monika V 65 Reputation points
2025-02-07T08:23:47+00:00

After updating the ClientID and ClientSecret, my Remote Event Receiver (RER), which was working previously, stopped functioning. The ClientID I was using expired recently, so I updated it to a new one and redeployed the app. However, I am now encountering the following error during app installation.

User's image

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
11,184 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Yanli Jiang - MSFT 28,881 Reputation points Microsoft Vendor
    2025-02-07T09:30:56.3866667+00:00

    Hi @Monika V ,

    Good days, thanks for posting in this forum.

    When updating the ClientID and ClientSecret for your Remote Event Receiver (RER), it's essential to ensure that the configuration in your web application is correctly updated. If you encounter errors during app installation after making these updates, consider the following steps:

    Update Configuration: Make sure that the ClientId and ClientSecret in your web.config file are updated correctly. The ClientSecret key should be changed to SecondaryClientSecret before adding the new ClientSecret.

    Check for Expired Tokens: If your previous ClientID was expired, ensure that any tokens associated with it are no longer being used.

    Service Bus Configuration: Verify that your service is hosted correctly in the Service Bus and that the endpoint is accessible. The error message you are encountering may indicate an issue with the endpoint configuration.

    SSL Certificate: If your RER is hosted on-premises and the add-in is in SharePoint Online, ensure that you are using a publicly trusted SSL certificate. Self-signed certificates are not acceptable in production for this scenario.

    Debugging: If the RER is not hitting breakpoints, check if the event is asynchronous, which may cause delays in hitting breakpoints.

    If you continue to face issues, reviewing the specific error message you are receiving can provide more insight into the problem.

    Please do let us know if you have any further queries.

    Kindly consider accepting the answer if the information provided is helpful. This can assist other community members in resolving similar issues. References:

    Debug and troubleshoot a remote event receiver in a SharePoint Add-in

    Registering and using Remote Event Receivers without having a dependency on Azure ACS

    Handle events in SharePoint Add-ins

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.