fixed
Remove GroupMemberById Documentation is being Updated
2 months ago by german zarkovich
Effective Version:
This change will be live in iMIS EMS 20.3.216, which is scheduled to be released at the end of November 2025.
What’s Changing:
Third-party developers and customers that rely on this endpoint will have better documentation about the parameters for using this endpoint correctly.
Example (Before – v20.3.216):
Request Endpoint:
DELETE /GroupMember/:GroupMemberId
Response:
<!DOCTYPE html>
<html>
<head>
<title>A potentially dangerous Request.Path value was detected from the client
</head>
<body bgcolor="white">
<span><H1>Server Error in '/' Application.<hr width=100% size=1 color=silver></H1>
<h2> <i>A potentially dangerous Request.Path value was detected from the client (<).</i> </h2></span>
<font face="Arial, Helvetica, Geneva, SunSans-Regular, sans-serif ">
<b> Description: </b>An unhandled exception occurred during the execution of the current web request. Please
review the stack trace for more information about the error and where it originated in the code.
<br><br>
<b> Exception Details: </b>System.Web.HttpException: A potentially dangerous Request.Path value was detected
from the client (<).<br><br>
<b>Source Error:</b> <br><br>
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code>
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. </code>
</td>
</tr>
</table>
<br>
<b>Stack Trace:</b> <br><br>
<table width=100% bgcolor="#ffffcc">
<tr>
<td>
<code><pre>
[HttpException (0x80004005): A potentially dangerous Request.Path value was detected from the client (<).]
System.Web.HttpRequest.ValidateInputIfRequiredByConfig() +678
System.Web.PipelineStepManager.ValidateHelper(HttpContext context) +52
</pre> </code>
</td>
</tr>
</table>
<br>
<hr width=100% size=1 color=silver>
<b>Version Information:</b> Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.9319.0
</font>
</body>
</html>
<!--
[HttpException]: A potentially dangerous Request.Path value was detected from the client (<).
at System.Web.HttpRequest.ValidateInputIfRequiredByConfig()
at System.Web.HttpApplication.PipelineStepManager.ValidateHelper(HttpContext context)
-->
Example (After – v20.3.216):
Request Endpoint:
DELETE /GroupMember?EntityId={GroupId}:{MemberId}
Response:
HTTP/1.1 200 OK
Impact:If you do not use the EntityId in your integrations, you are are not going to be able to utilize the endpoint. If you do not use the GroupMember Delete endpoint in your integrations, you are unaffected by this change and no action is required
Please review your current implementations.