Log in

Login to your account

Username *
Password *
Remember Me

Create an account

Fields marked with an asterisk (*) are required.
Name *
Username *
Password *
Verify password *
Email *
Verify email *
Captcha *
×

Error

Le fichier .obs importé est incorrect. Ce n'est pas un fichier au format Scénario Obsewhere !

Ce scénario est proposé dans un pack: Payant

Use case Objective

In Joomla administration, you wish to limit access to some users, to menus or menu items settings. You need more security in a simple process, without losing flexibility.

This use case can apply to all menus, some menus types, some menu items.
This use case can also apply to any feature in Joomla administration.
You can also display a simple message without blocking access.

Joomla Feature

The main solution, integrated to Joomla, is the well-known ACLs, which allow to set users rights in a very powerfull and precise way. This ACL structure requires a global analysis of all administration features and implies very rigorous settings.
Moreover, due to this deep analysis, the ACLs are dedicated to be lifetime (and not temporary), and can't be set for some users and some features.

What Obsewhere brings you

You can limit access to menus or menu items. The process is not actually blocking access but setting a redirection when the user attempts to display the forbidden url. For instance if the user should not reach menu items, he can be redirected to articles list, and a message can be displayed to remind him his access restriction, and why he is redirected.

As mentionned in "Use case Objective", you can simply display a message (like an inline information) associated to any url, specificly in administration. In that case, there's no redirection and the feature is accessible.

This process, relying on url in administration is :

  • standard Joomla environment,
  • easy and quick to be set,
  • temporary or permanent,
  • possible for 1 user, several user user groups,
  • independant from ACLs,

Ce scénario est proposé dans un pack: Payant

Use case Objective

Real-time administrator's alert in case of flooding (X connections in short time period) against your Joomla website.
This use case concerns core Joomla users connections. Monitoring connections through components would be other use cases.

Joomla Features

As far as we know, this feature of real-time notification doesn't exist among Joomla firewall components.

What Obsewhere brings you

  • the insurance to be alerted in real-time in case of flooding, while a classical firewal rarely provide real-time notification,
  • reinforce your real-time website monitoring process, and reduce time to react and take more protection measures,
  • keep track of the attack event.

Ce scénario est proposé dans un pack: Payant

Use case Objective

Avoid unwanted users from specific countries. Sometimes those registrations happen from time to time and are difficult to spot.
The target is also to preserve your bounce rate due to useless registrations.

Joomla Feature

As far as we know, this feature doesn't exist to prevent from unwanted Acymailing users.

What Obsewhere brings you

  • a feature only available for Acymailing, at the moment,
  • increase your security level and get a new opportunity to conform to GDPR,
  • clean up your newsletter recipient base.

Ce scénario est proposé dans un pack: Payant

Use case Objective

You wish to avoid email injections through Joomla contact form ("com_contact"), from some suspicious countries.
Similar to user domain filter settings, you wish to ban some focused countries (their country code, technically named as TLD).
Joomla standard contact form is an old feature, very well known by hackers. This kind of security seems essential.

Joomla Feature

As far as we know, this feature doesn't exist to prevent from unwanted country senders..

What Obsewhere brings you

  • increase your site's security level and consequently improve your GDPR compliance : Obewhere country filter is called before form process.
  • you can ban as many countries as you want,
  • possibility to set an alerting email to administrator, in case of emails injections from banned TLD.

Ce scénario est proposé dans un pack: Payant

Use case Objective

You wish to oblige users to periodically reset their password, for instance each 1st quarter day.

This process would be part of your security measures and GDPR conformity.

The parameter underneath, set to "Yes" automatically, will oblige the user to reset his password at the next connexion. 

require password reset

Joomla Feature

This feature is currently : :

  • manual
  • to be set user by user

What Obsewhere brings you

  • define the date and reset frequency,
  • automatically modify the setting to reset the password,
  • impact all users or only groups.