Discussions
"Refresh token lifetime" in the SSO doesn't seem to be honoured
I have an SSO application setup that works, but the "Refresh token lifetime" value doesn't seem to be honoured across the problem. I have the Refresh token lifetime (minutes) variable set to 1440 minutes, but the refresh value I get back following a call to /api/token is "expires_in":1199. It's always 1199 regardless of the value I set it to in the iMIS configuration. Do I need to keep resetting it? Thanks.
Extending AsiMembershipProvider
Hello,
Google can't crawl the website
Greetings all,
Panels inheriting AtomPanelBase must have non-null Atom property - but it does!
I'm working with a C#-based, deploy-the-binary kind of iPart. I'm working in iMIS 2017 with Service Pack I, recently upgraded from 20.2.9. The iPart was deployed and working before the upgrade, and continued to work after the upgrade. Now we're trying to configure the iPart in content and getting this exception:
Can someone please comment on the examples on this site
I recently ran into an issue where my (very simple) REST code stopped working. I resorted to cutting and pasting from this site and it continued to fail with nothing but 401 errors. It wasn't until I realized there might be an error in the documentation that I got it working again. When calling the API via JavaScript, do you use the "scheduler" folder structure or the "site" folder structure? I ask because if you start at https://developer.imis.com/docs/querying-data-with-rest, the example given for "Get a list of party objects", shows as https://testapi.imis.com/sdkdemo/api/party. But if you click that link and scroll down to the documentation detail it shows as https://testapi.imis.com/Asi.Scheduler_SDKDemo/api/Party. I had switched to the scheduler URL somewhere along the line and that was the problem, once I switched back things were good.
Looking for advice before deleting from CommunicationLog table
A client has thousands of messages in the CommunicationLog with values of 0 in the Sent, Delivered, and Not Delivered columns. They were added here over time from a runaway Process Automation task, which I need to investigate and modify to prevent it from writing these ghost records in the future. As for the historical records already written, I was thinking of writing a SQL query to delete them from the table. Before taking that step, I was hoping someone could provide some guidance. Will deleting from this table pose a problem? Two related tables give me pause for concern – CommunicationLogEvent and CommunicationLogRecipient. These two seem to be related to CommunicationLog through the CommunicationLogKey column. ASI tech support said this type of support goes beyond the scope of their responsibilities. I was also unable to find any documentation on this topic. Any advice would be greatly appreciated.
IMIS REST API - Write to Non iMIS Table
Does anyone know if the iMIS REST API can be used to write data to a non IMIS table?
Can we get a simple pure C# example of Adding the RequestVerificationToken to headers for GET
(I couldn't resist modeling on Jack's post.)
How to relate Party to User using REST?
There doesn't seem to be a good, natural way to get from a Party to a User.
SSO Procedure Questions
I've got the new SSO process working, in that I can pass someone to our iMIS site and get them back to the external site with valid tokens, but I have two questions about this process that I can't find information on or get working: