EagleSafe
EN
Talk to us

Products · WAM

EagleSafe WAM

Put your websites and applications behind EagleSafe: one sign-in, a second factor where it matters, the same people as in your directory. Nothing to rewrite.

← All products

What it does

  • One sign-in for your applications

    Portals, intranets, web business software and private areas open with the same identity used for everything else, with no separate sign-in for each.

  • A second factor with no development

    Authenticator app, email or push notification, even on applications that don’t support it: EagleSafe adds it, not the application.

  • Applications stop handling passwords

    Sign-in is handed over to EagleSafe: no user lists in every application, no passwords to reset one by one.

  • Open standards

    Works with any application that supports OpenID Connect / OAuth 2.0 or SAML, the standards used by CMSs, intranets, web business software, portals and cloud software.

  • Sign-in pages with your branding

    People see your logo and your name when they sign in, not a supplier’s.

  • Access and revocation in one place

    When someone leaves the company, or is removed from a group, they immediately lose access to every application at once.

How it works

Four steps, no changes to the application’s code: it uses the standard sign-in the application already supports.

From registration to first sign-in

  1. Register the application

    In EagleSafe, as a custom application: a name, its address and the sign-in type, OpenID Connect / OAuth 2.0 or SAML.

  2. The application hands over sign-in

    In the application’s settings, you set EagleSafe as the sign-in system. From then on, it no longer asks for passwords.

  3. People sign in as usual

    Anyone opening the application goes through the EagleSafe sign-in page, with your logo, signs in with their identity and returns to the application already authenticated.

  4. You set the rules

    Your directory groups decide who can sign in and with which factor, and you can change that at any time without touching the application.

One point of control

  • Your people are always the same, synced from the directory or recognised by external providers: no user list for every site.
  • When someone leaves the company, or is removed from a group, they immediately lose access to every application at once.
  • Every sign-in to every application goes into the same log: who, when, from where, with which factor.
  • Passwords, lockout, session length and second factor apply to every application and are changed in one place.

Use cases

  • A professional firm’s client portal

    Accountants, lawyers, consultants: clients sign in with a second factor to download their documents, and the firm doesn’t manage any passwords.

  • Intranet and web business software

    One sign-in for both, with the company domain identity: nobody has to remember extra credentials in the morning.

  • Your website’s private area

    Price lists, technical documentation, reseller materials: protected with a second factor in an afternoon, with no development.

  • Cloud software

    CRM, ticketing, collaboration platforms: if they support SAML or OpenID Connect, they connect to EagleSafe and use your company identities.

  • Agent and supplier portal

    External users can reach only the applications they need, with a second factor, and lose access the moment the relationship ends.

  • Internal tools and dashboards

    Admin panels, reports and data dashboards: visible only to the right groups, with a second factor for the most sensitive ones.

  • Training and documentation

    E-learning platforms and company knowledge bases: one sign-in for staff and contractors, managed from the directory.

  • Test environments

    Test and preview versions of your applications stay visible only to the people working on them, with no shared passwords.

Applications that support neither OpenID Connect nor SAML need an extra step, assessed case by case. The number of protected applications is agreed in your contract.

Frequently asked questions

Do we have to change our applications?

No, if they support OpenID Connect / OAuth 2.0 or SAML: you set up sign-in in the application’s settings, without writing any authentication code.

Which applications are compatible?

Any that support OpenID Connect / OAuth 2.0 or SAML: most CMSs, intranets, web business software, client portals and cloud software.

Can we require a second factor on some applications only?

Yes. You decide on the second factor per application or per directory group: for everyone, for some groups or only on the most sensitive applications.

Who decides who can use each application?

Your directory groups: one group per application or one group for several, managed with the tools you already use.

Can external users sign in too?

Yes: clients, agents or suppliers can have local users in EagleSafe or sign in with an external provider, with access limited to the applications they need.

What gets logged?

Every sign-in to every application, in the same log: who, when, from where and with which factor.

What about applications that don’t support these standards?

They need an extra step, assessed case by case: talk to us and we’ll tell you how to proceed.

Works with

Talk to us

Tell us how your business works: we’ll show you how EagleSafe protects identities, access and your network.

Talk to us

Are you a reseller or an MSP? EagleSafe is also offered to customers through partners: discover the Eagle Networks partner programme.

Partner programme