Alternatives to RSA SecurID logo

Alternatives to RSA SecurID

Duo, Okta, Authy, Auth0, and Amazon Cognito are the most popular alternatives and competitors to RSA SecurID.
3
9
+ 1
0

What is RSA SecurID and what are its top alternatives?

It is a mechanism developed by Security Dynamics for performing two-factor authentication for a user to a network resource.
RSA SecurID is a tool in the User Management and Authentication category of a tech stack.

Top Alternatives to RSA SecurID

  • Duo

    Duo

    Duo is a next-generation package manager that blends the best ideas from Component, Browserify and Go to make organizing and writing front-end code quick and painless. ...

  • Okta

    Okta

    Connect all your apps in days, not months, with instant access to thousands of pre-built integrations - even add apps to the network yourself. Integrations are easy to set up, constantly monitored, proactively repaired and handle authentication and provisioning. ...

  • Authy

    Authy

    We make the best rated Two-Factor Authentication smartphone app for consumers, a Rest API for developers and a strong authentication platform for the enterprise. ...

  • Auth0

    Auth0

    A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications. ...

  • Amazon Cognito

    Amazon Cognito

    You can create unique identities for your users through a number of public login providers (Amazon, Facebook, and Google) and also support unauthenticated guests. You can save app data locally on users’ devices allowing your applications to work even when the devices are offline. ...

  • JSON Web Token

    JSON Web Token

    JSON Web Token is an open standard that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. ...

  • OAuth2

    OAuth2

    It is an authorization framework that enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. ...

  • Spring Security

    Spring Security

    It is a framework that focuses on providing both authentication and authorization to Java applications. The real power of Spring Security is found in how easily it can be extended to meet custom requirements. ...

RSA SecurID alternatives & related posts

Duo logo

Duo

13
29
1
A next-generation package manager for the front end
13
29
+ 1
1
PROS OF DUO
  • 1
    Lean and efficient
CONS OF DUO
    Be the first to leave a con

    related Duo posts

    Okta logo

    Okta

    273
    564
    53
    Enterprise-grade identity management for all your apps, users & devices
    273
    564
    + 1
    53
    PROS OF OKTA
    • 12
      REST API
    • 7
      SAML
    • 5
      OIDC OpenID Connect
    • 4
      Easy LDAP integration
    • 4
      User Provisioning
    • 4
      Protect B2E, B2B, B2C apps
    • 3
      Tons of Identity Management features
    • 3
      SSO, MFA for cloud, on-prem, custom apps
    • 3
      Easy Active Directory integration
    • 3
      API Access Management - oAuth2 as a service
    • 3
      Universal Directory
    • 1
      SOC2
    • 1
      SWA applications Integration
    CONS OF OKTA
    • 2
      Pricing is too high
    • 1
      Okta verify (Multi-factor Authentication)

    related Okta posts

    Authy logo

    Authy

    138
    135
    1
    The easiest way to add Two-Factor Authentication to any website or app.
    138
    135
    + 1
    1
    PROS OF AUTHY
    • 1
      Google Authenticator-compatible
    • 0
      1
    CONS OF AUTHY
    • 2
      Terrible UI on mobile

    related Authy posts

    Auth0 logo

    Auth0

    996
    1.5K
    198
    Token-based Single Sign On for your Apps and APIs with social, databases and enterprise identities
    996
    1.5K
    + 1
    198
    PROS OF AUTH0
    • 59
      JSON web token
    • 30
      Integration with 20+ Social Providers
    • 19
      SDKs
    • 19
      It's a universal solution
    • 14
      Amazing Documentation
    • 11
      Heroku Add-on
    • 8
      Enterprise support
    • 7
      Extend platform with "rules"
    • 7
      Great Sample Repos
    • 4
      Azure Add-on
    • 3
      Passwordless
    • 3
      Easy integration, non-intrusive identity provider
    • 2
      It can integrate seamlessly with firebase
    • 2
      Great documentation, samples, UX and Angular support
    • 2
      Polished
    • 2
      On-premise deployment
    • 2
      Ruby
    • 1
      Active Directory support
    • 1
      SOC2
    • 1
      Will sign BAA for HIPAA-compliance
    • 1
      Great support
    • 0
      A';P[];Æ`/
    CONS OF AUTH0
    • 11
      Pricing too high (Developer Pro)
    • 7
      Poor support
    • 4
      Status page not reflect actual status
    • 3
      Rapidly changing API

    related Auth0 posts

    Stephen Gheysens
    Senior Solutions Engineer at Twilio · | 12 upvotes · 128.5K views

    Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

    My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

    See more

    I'm starting a new React Native project and trying to decide on an auth provider. Currently looking at Auth0 and Amazon Cognito. It will need to play nice with a Django Rest Framework backend.

    See more
    Amazon Cognito logo

    Amazon Cognito

    431
    653
    32
    Securely manage and synchronize app data for your users across their mobile devices
    431
    653
    + 1
    32
    PROS OF AMAZON COGNITO
    • 13
      Backed by Amazon
    • 7
      Manage Unique Identities
    • 3
      MFA
    • 3
      Work Offline
    • 2
      Store and Sync
    • 1
      It works
    • 1
      Integrate with Google, Amazon, Twitter, Facebook, SAML
    • 1
      SDKs and code samples
    • 1
      Free for first 50000 users
    CONS OF AMAZON COGNITO
    • 3
      Massive Pain to get working
    • 2
      Login-UI sparsely customizable (e.g. no translation)
    • 2
      Documentation often out of date
    • 1
      MFA: there is no "forget device" function
    • 1
      Hard to find expiration times for tokens/codes
    • 1
      Lacks many basic features
    • 1
      There is no "Logout" method in the API
    • 1
      No recovery codes for MFA
    • 1
      Difficult to customize (basic-pack is more than humble)
    • 1
      Only paid support
    • 1
      Docs are vast but mostly useless

    related Amazon Cognito posts

    I'm starting a new React Native project and trying to decide on an auth provider. Currently looking at Auth0 and Amazon Cognito. It will need to play nice with a Django Rest Framework backend.

    See more
    JSON Web Token logo

    JSON Web Token

    424
    174
    0
    A JSON-based open standard for creating access tokens
    424
    174
    + 1
    0
    PROS OF JSON WEB TOKEN
      Be the first to leave a pro
      CONS OF JSON WEB TOKEN
        Be the first to leave a con

        related JSON Web Token posts

        Repost

        Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

        Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

        Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

        Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

        See more

        Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku. However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

        Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

        Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

        Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

        See more
        OAuth2 logo

        OAuth2

        384
        379
        0
        An open standard for access delegation
        384
        379
        + 1
        0
        PROS OF OAUTH2
          Be the first to leave a pro
          CONS OF OAUTH2
            Be the first to leave a con

            related OAuth2 posts

            Joshua Dean Küpper
            CEO at Scrayos UG (haftungsbeschränkt) · | 7 upvotes · 254.4K views

            As the access to our global REST-API "Charon" is bound to OAuth2, we use Keycloak inside Quarkus to authenticate and authorize users of our API. It is not possible to perform any un-authenticated requests against this API, so we wanted to make really sure that the authentication/authorization component is absolutely reliable and tested. We found those attributes within Keycloak, so we used it.

            See more
            Isaac Ogunleye
            Backend Developer at Coast research Institute · | 5 upvotes · 30.9K views
            Shared insights
            on
            Passport
            OAuth2

            My teammates and I are arguing on which library to use for our local and social authentication in our express app between OAuth2 and Passport. I went for Passport cause I personally like it, and it seems easier to implement with good docs, but some of my teammates think it's less secure than OAuth2. So any advice please would be appreciated. Thanks 🙏🏻

            See more
            Spring Security logo

            Spring Security

            376
            365
            4
            A powerful and highly customizable authentication and access-control framework
            376
            365
            + 1
            4
            PROS OF SPRING SECURITY
            • 2
              Easy to use
            • 2
              Java integration
            CONS OF SPRING SECURITY
              Be the first to leave a con

              related Spring Security posts