Security related settings.

Security related settings.

After updating to version 14001, we are seeing a lot of “rate limit reached for a non-login URL” notifications.

Solution:


Please go to Admin - Global Settings - Security Settings - Advanced in which you will find the below option. 


By disabling the below option, the notifications will not appear. 









                  New to ADSelfService Plus?

                    • Related Articles

                    • Query to show Site and its related settings(MSSQL & PGSQL)

                      Tested in Build PGSQL (14300) or MSSQL (14306) Go to Reports-New Query Report and execute the query. select adef.org_name "Account Name",sdef.siteid "Site ID", sdo.name "Site Name", siteconf.settingdetail "Related Settings", CASE WHEN ...
                    • Difference between Default Settings, Custom Settings and Copy Default

                      In SDP-MSP, the configurations are done based on the site, under Admin >> Sites >> Related Settings, we have 3 different types of settings, Copy Default Settings, Refer Settings and Custom Settings for the features mentioned under How to Configure ...
                    • Security Settings | Common Tweaks: Hide concurrent login banner.

                      Hide concurrent login banner: We will show a banner in the bottom right, when the same user logs in from another instance. Some customers want to disable these alerts. To modify this behaviour, connect to the database and run the following query: ...
                    • Security settings, Logo and other customisation for mobile app

                      Requirement: Security settings for mobile app is waiting for release in 14830 build version. In addition to this, server side support for separate logo for mobile app is currently under development. Meanwhile, customers are requesting customisations ...
                    • 14740: Mail related fixes

                      Issue: The fix contains the below fixes 1. The Graph API calls timeout increased to 100s. This has been fixed in 14760 version on upgrading the microsoft SDK to 2.0.21 version. 2. The user thread wait time to semaphore acquire (wait time to acquire ...