Discussions

Hello, I'm concerned about this situation: I just created a Public User in Imis and didn't change any permission to it.

We have an SSO using the out of the box ipart and process that is working with 20.2 and was working with 20.3 until the recent August changes to the refresh token. I understand that it is only good for 1 hour and can be invalidated when the cache is cleared. What would cause the cache to be cleared? Also, can you use the refresh token more than once?

I am trying to enable CORS on the api so I can make cross-origin calls. The API does not understand the OPTIONS method that is being sent by the browser when I make an XHR request using axios. This results in a 405 for the options preflight request and a CORS failure. What is the quickest way to enable this? I am unsure how to enable the necessary CORS features on a WCF service without access to the entry point.

Has anyone seen this error when registering an Event? It occurs only in the Public view website (registrations occur properly from Staff View).

Hello, the MembershipWebService has a ChangeUsername function (with parameters for the old username and new username), and this works fine. However, it automatically sends an email to the user notifying them of the update, and including their new automatically-generated password in PLAINTEXT. (This is for 20.2.64.8807.)

As we start to look at transitioning from iMIS 20.2 2015 to iMIS 20.2 2017 and then hopefully to the Cloud in the future, we are trying to figure out how we can do REST API request that the general public would perform searches for individuals for example, their certification information. I see that in iMIS 20.2 2017, we are required to have a bearer token and that requires logging in, but what if the user does not have a login and we need to enable searches?

Hey Jeremy,

I'm trying to test the API endpoint for updating a Party