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

Question

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.

Answer 1

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

Answer 2

Hi.

Getting the below error.

System.FormatException: The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.

 

client secret that was no longer in a base64 encoded format. However, the TokenHelper class, which is used in the SharePoint add-in, expects the client secret to be in base64 encoding.

 

can you please help me ?