Partner returned 403/Forbidden
If end-users complain that after validation with BioSig-ID™ they are seeing 404/Forbidden errors, then that means there is an issue with the partner environment.
Known cause is that CloudFlare is blocking the server-to-server request.
CloudFlare > WAF > Security Events > Activity Log
There should be log entries listed that confirm requests are being blocked from verifyexpress.com (IP = 23.100.25.17).
By creating an IP Access rule for 23.100.25.17 to allow this traffic, everything should become functional again.
Related Articles
Integration Options
Integration Introduction The BioSig-ID™ Application and any related features are integrated through air-gapped interfaces each having their respective inbound and outbound area. This allows for the flexibility to quickly design and develop new ...
User Summary Report
About this Report Summarizes user totals for each partner and account This report will show the total active users and new users for a defined time frame. How to run this report Settings and selections: Date Range - Select one of the predefined dates ...
Registration/Validation/Attendance Report
About this report Provides a summary of user enrollment and validation activity. This report can be filter down to a specific course in a specific session. If ran across a session, the course name will show with all validations within each course and ...
User Attendance Grid
About this report This report provides a grid-like overview of the student's attendance by date and time range. Uses for this report include: Census date reporting to identify student activity Compare the number of students registered to inactive ...
User Courses
About this report Lists Students and Courses they are active in. This report is helpful to determine if multiple students are enrolled in the same courses each session and if perhaps there is a paid individual taking the courses for a group of ...