![\"A](\"/31897617f8cfd303cc4a03b4950ccab7/how-mfa-works.webp\")
What is Web Accessibility?
\nWeb Accessibility (often stylized “a11y”), is the practice of ensuring that your websites and web applications are accessible by people with disabilities of many kinds.
\nSome examples of common disabilities which we need to consider are: Blindness and visual impairment, deafness and hearing difficulties, motor skill impairment, and many more.
\nThe common categories of disabilities include:
\nThis list was taken from the W3C Web Accessibility Initiative (WAI). A link to their resources can be found at the bottom.
\nWhat is Semantic HTML? What is its correlation with Web Accessibility?
\nHTML semantics refers to conveying meaning through the use of HTML elements. An example of semantic HTML would be using <header>, <main>, <footer>, and other content-specific tags when applicable. Unsemantic HTML would be using <div> or <span> tags for every use-case.
Images and “alt” attributes
\nUsers who are visually impaired may encounter trouble when the content of a website relies on an image. Luckily, there are precautions that we - as developers - can take to ensure that their user experience does not suffer because they are unable to see images.
\nThe easiest way to do this is to add an alt attribute to all of your <img> tags. This way, screen readers will be able to describe the image to the user. Here are a few suggestions and best practices for writing alt text:
Do not include words like “image”, or “picture”. It is redundant, because the screen reader will notify the user that it’s an image. An exception to this would be if the image is of a painting, or an illustration. In this case, emphasizing that is fine, because you want the user to know that it’s specifically a painting, as opposed to any image.
\nAlways include the alt attribute, even if you don’t want the screen reader to read it. If you have a decorative image (one that is simply cosmetic, and not necessary for the site), then you can add an alt tag and assign it to an empty string. In this case, the image will be ignored by the screen reader. If this is neglected, the screen reader may read the file name instead, which may not be particularly helpful.
\nForm Labels and ARIA Labelling
\nUsers with screen readers will need some way to differentiate between multiple inputs on a single form. Without labels, the user will have a difficult time figuring out what each input is for.
\nThe easiest way to implement form labelling is with the HTML <label> tag. The <label> element uses an attribute called for in order to form a relationship with the ID of the <input> tag.
Another way to give context to a screen reader is with the ARIA aria-labelledby attribute. This attribute can be placed on (but not limited to) <input> tags, and then reference the id of the label. You can use <label for=””> in conjunction with <input aria-labelledby=””> in order to provide extra support and maximize compatibility.
Buttons and Tabindices
\nButtons should use <button> tags (or <input type=”submit”> if applicable), rather than <a>, <span>, <div>, or anything else that doesn’t have semantic meaning for clickable buttons. Often people choose to use these tags, because they want to clear all styling and not have default <button> styling. This is ill-advised because <button> tags come with a ton of functionality built-in, an important part being its tabindex. A user who isn’t able to use a mouse, and must navigate the site with their keyboard, will press the tab key to jump through interactive elements. Standard <div> tags are not tabbable by default, and assigning a tabindex to it manually can break the flow of the natural tabindices of the page.
Other Semantic HTML tags
\nOther than images and forms, there are still many ways to provide the best accessibility possible. Semantic HTML tags are useful because they describe the content and the relationship with your overall page. Using appropriate, accurate tags such as <article>, <aside>, <section> will give screen readers an idea of what the role is for those sections.
Other elements such as <h1> and other heading tags should be carefully planned before sprinkled throughout your webpage. The <h1> through <h6> tags should form direct relationships with each other in order to differentiate their meaning. Headings with lower importance (relative to the previous heading) can be used to start new subsections within its current section. Your different page sections can even use aria-labelledby to point to its corresponding heading in order to label your sections accurately.
The full W3C specification on HTML semantics can be found at: W3C Recommendation.
\nMore information about the varying disabilities and barriers can be found at: Diverse Abilities and Barriers
\n","frontmatter":{"date":"July 24, 2019","updated_date":null,"description":null,"title":"Introduction to Web Accessibility with Semantic HTML5","tags":["HTML5","HTML","Web Accessibility","Semantic HTML5"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/70f4300c1f86c6d8e337f40979e66dea/58556/handicapped.webp","srcSet":"/static/70f4300c1f86c6d8e337f40979e66dea/61e93/handicapped.webp 200w,\n/static/70f4300c1f86c6d8e337f40979e66dea/1f5c5/handicapped.webp 400w,\n/static/70f4300c1f86c6d8e337f40979e66dea/58556/handicapped.webp 800w,\n/static/70f4300c1f86c6d8e337f40979e66dea/cc834/handicapped.webp 1024w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Greg Sakai","github":null,"avatar":null}}}},{"node":{"excerpt":"A basic example of a JavaScript event Events, in JavaScript, are occurrences that can trigger certain functionality, and can result in…","fields":{"slug":"/engineering/javascript-events-bubbling-capturing-and-propagation/"},"html":"A basic example of a JavaScript event
\nEvents, in JavaScript, are occurrences that can trigger certain functionality, and can result in certain behaviour. A common example of an event, is a “click”, or a “hover”. You can set listeners to watch for these events that will trigger your desired functionality.
\nWhat is “propagation”?
\nPropagation refers to how events travel through the Document Object Model (DOM) tree. The DOM tree is the structure which contains parent/child/sibling elements in relation to each other. You can think of propagation as electricity running through a wire, until it reaches its destination. The event needs to pass through every node on the DOM until it reaches the end, or if it is forcibly stopped.
\nEvent Bubbling and Capturing
\nBubbling and Capturing are the two phases of propagation. In their simplest definitions, bubbling travels from the target to the root, and capturing travels from the root to the target. However, that doesn’t make much sense without first defining what a target and a root is.
\nThe target is the DOM node on which you click, or trigger with any other event.
\nFor example, a button with a click event would be the event target.
\nThe root is the highest-level parent of the target. This is usually the document, which is a parent of the , which is a (possibly distant) parent of your target element.
\nCapturing is not used nearly as commonly as bubbling, so our examples will revolve around the bubbling phase. As an option though, EventTarget.addEventListener() has an optional third parameter - which takes its argument as a boolean - which controls the phase of the propagation. The parameter is called useCapture, and passing true will cause the listener to be on the capturing phase. The default is false, which will apply it to the bubbling phase.
\nOnce you trigger the event, it will propagate up to the root, and it will trigger every single event handler which is associated with the same type. For example, if your button has a click event, during the bubbling phase, it will bubble up to the root, and trigger every click event along the way.
\nThis kind of behaviour might not sound desirable - and it often isn’t - but there’s an easy workaround...
\nEvent.stopPropagation()
\nThese two methods are used for solving the previously mentioned problem regarding event propagation. Calling Event.stopPropagation() will prevent further propagation through the DOM tree, and only run the event handler from which it was called.
\n<!--Try it-->function first() {\n console.log(1);\n}\nfunction second() {\n console.log(2);\n}\nvar button = document.getElementById("button");\nvar container = document.getElementById("container");\nbutton.addEventListener("click", first);\ncontainer.addEventListener("click", second);In this example, clicking the button will cause the console to print 1, 2. If we wanted to modify this so that only the button’s click event is triggered, we could use Event.stopPropagation() to immediately stop the event from bubbling to its parent.
\nfunction first(event) {\n event.stopPropagation();\n console.log(1);\n}This modification will allow the console to print 1, but it will end the event chain right away, preventing it from reaching 2.
\nHow does this differ from Event.stopImmediatePropagation()? When would you use either?
<!--Try it-->function first(event) {\n console.log(1);\n}\nfunction second() {\n console.log(2);\n}\nfunction third() {\n console.log(3);\n}\nvar button = document.getElementById("button");\nvar container = document.getElementById("container");\nbutton.addEventListener("click", first);\nbutton.addEventListener("click", second);\ncontainer.addEventListener("click", third);Let’s suppose we wanted to add a third function, which prints 3 to the console. In this scenario, we will also move the second function to also be on the button. We will apply third to the container now.
\nLong story short: we have two event handlers on the button, and clicking <div#container> will now print 3.
\nWhat will happen now? This will behave the same as before, and it will propagate through the DOM tree, and print 1, 2, 3, in that order.
\nHow does this tie in to Event.stopPropagation() and Event.stopImmediatePropagation()?
Adding Event.stopPropagation() to the first function, like so, will print 1, 2 to the console.
\nfunction first(event) {\n event.stopPropagation();\n console.log(1);\n}This is because Event.stopPropagation() will immediately prevent all click events on the parent from being triggered, but it does not stop any other event handlers from being called.
\nAs you can see in our example, our button has two click handlers, and it did stop the propagation to its parents. If you wanted to stop all event handlers after the first, that’s where Event.stopImmediatePropagation() comes in.
\nfunction first(event) {\n event.stopImmediatePropagation();\n console.log(1);\n}Now, the first function really will stop the parent click handlers, and all other click handlers. The console will now print just 1, whereas if we simply used Event.stopPropagation(), it would print 1, 2, and not including either would print 1, 2, 3 .
\n","frontmatter":{"date":"July 22, 2019","updated_date":null,"description":null,"title":"JavaScript Events: Bubbling, Capturing, and Propagation","tags":["JavaScript","JavaScript Events"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.3333333333333333,"src":"/static/53a3895e9c38870937a9136813ac9e10/0ce14/bubbles.webp","srcSet":"/static/53a3895e9c38870937a9136813ac9e10/61e93/bubbles.webp 200w,\n/static/53a3895e9c38870937a9136813ac9e10/1f5c5/bubbles.webp 400w,\n/static/53a3895e9c38870937a9136813ac9e10/0ce14/bubbles.webp 772w","sizes":"(max-width: 772px) 100vw, 772px"}}},"author":{"id":"Greg Sakai","github":null,"avatar":null}}}},{"node":{"excerpt":"What is Multi Factor Authentication (MFA)? Multi Factor Authentication (MFA) is a security process that requires users to verify their…","fields":{"slug":"/identity/what-is-multi-factor-authentication/"},"html":"Multi Factor Authentication (MFA) is a security process that requires users to verify their identity using two or more authentication factors before accessing an account, application, or system.
\nUnlike traditional password-based logins, MFA adds an extra layer of security by demanding additional verification, reducing the risk of unauthorized access. For instance, a user must complete a second verification process after providing their username and password to access certain platforms or resources.
\nMFA is widely used in various industries, including e-commerce, media & communication, healthcare, and finance, to protect user accounts from cyber threats. Hundreds of organizations have benefited by integrating MFA. See how to integrate MFA into security policies to mitigate risks associated with credential theft and data breaches.
\nCybercriminals are constantly exploiting weak credentials and gaining access to sensitive systems. Here’s where we get an answer to the question- Why is MFA important?
\nSince we’ve learned what MFA is and why it’s important, let’s understand how it works. The MFA process is straightforward yet highly effective. Here’s how it works:
\nUnderstanding how MFA works is crucial for organizations implementing strong security policies.
\nMFA can be implemented in various ways, and organizations can choose the most suitable method based on their security needs and user convenience.
\n
Different MFA methods provide varying levels of security and convenience. Here are the most commonly used types of multi-factor authentication:
\nA TOTP is a temporary passcode generated by an authentication app (e.g., Google Authenticator or Microsoft Authenticator). The code expires shortly, reducing the risk of unauthorized access.
\nPush notification MFA is one of the convenient MFA factors that allows seamless authentication. It involves sending a push notification to a registered mobile device and asking the user to approve or deny the login attempt.
\nAn SMS-based MFA solution sends a one-time passcode (OTP) to a user’s mobile phone via text message. The user must enter the OTP to complete authentication.
\nA hardware token is a physical device that generates OTPs or connects via USB/NFC to authenticate the user.
\nThis method uses inherent factors like fingerprint scans, facial recognition, or iris scans for verification.
\nBiometric authentication is gaining popularity because of its ease of use and strong security. Many modern devices, including smartphones and laptops, integrate biometric authentication as an additional layer of security.
\n![\"Buyers](\"/b2d3a16b02ab56f63d8a8a720ca22b86/eb-buyers-guide-to-multi-factor-authentication.webp\")
Authentication factors are categorized into different types based on what the user knows, has, or is. These MFA factors play a key role in strengthening security.
\nExamples include passwords, PINs, or security questions.
\nExamples include smartphones, security keys, and smart cards.
\nThese involve biometric authentication methods such as fingerprints, voice recognition, or facial scans.
\nThese include behavioral patterns like keystroke dynamics and mouse movement patterns.
\nBehavioral authentication is an emerging MFA technology that continuously analyzes user behavior to detect anomalies and prevent unauthorized access.
\nMany people confuse both terms and are unable to decide between 2FA and MFA. When it comes to 2FA vs MFA, the difference is quite simple:
\nMFA is more secure than 2FA since it provides additional layers of protection. Organizations handling sensitive data or focusing on enterprise security often prefer MFA over 2FA to ensure stronger security.
\nWhen we talk about an advanced security measure, Adaptive MFA is undoubtedly a game-changer that analyzes user behavior and risk levels to determine when to prompt for authentication.
\nIf a login attempt appears risky (e.g., new device, unusual location), the system triggers additional authentication steps.
\nAdaptive MFA helps balance security and user convenience by requiring additional verification only when necessary.
\nHere are some MFA examples used by businesses and individuals:
\nWhen it comes to the benefits of MFA, the list is endless; here’s a list of a few benefits that you get:
\nMFA protects against unauthorized access by adding extra layers of verification beyond passwords. It significantly reduces the risk of credential-based attacks and data breaches.
\nBusinesses can implement MFA solutions to secure digital transactions, remote work setups, and cloud applications. This allows organizations to safely expand their digital services without compromising security.
\nMFA helps businesses prevent fraudulent transactions and unauthorized account access. It is especially crucial for industries like banking and e-commerce, where financial fraud is a major concern.
\nCustomers feel more confident using services that implement strong authentication measures. A well-implemented MFA system reassures users that their sensitive information is protected, leading to improved customer retention and brand reputation.
\nMany industries, such as healthcare and finance, require MFA to comply with strict data protection regulations. Implementing MFA ensures that businesses meet compliance standards like GDPR, HIPAA, and PCI DSS.
\nSee how one of our clients- SafeBridge, leveled up security with LoginRadius MFA.
\nLoginRadius Multi-Factor Authentication makes security effortless. With flexible options like OTPs, biometrics, and authenticator apps, you can add an extra layer of protection without disrupting the user experience.
\nMoreover, LoginRadius’ adaptive MFA intelligently detects risk—only stepping in when needed, like an unusual login attempt. Best of all, you can integrate LoginRadius MFA into your app or website within minutes, with developer-friendly APIs and seamless workflows. Strong security, easy implementation, and a frictionless login experience—all in one solution.
\nGoogle Authenticator is a mobile app that generates time-based one-time passwords (TOTP) for multi-factor authentication (MFA).
\nIt provides an additional layer of security by requiring users to enter a unique 6-digit code, which refreshes every 30 seconds, along with their password during login. This method helps protect accounts from unauthorized access and is widely used across various platforms for secure authentication.
\nYubico provides hardware-based multi-factor authentication (MFA) solutions through its YubiKey devices. YubiKeys enhances security by requiring physical authentication in addition to a password, protecting accounts from phishing and unauthorized access.
\nThey support multiple authentication methods, including FIDO2, U2F, OTP, and Smart Card authentication, making them compatible with a wide range of platforms. Unlike SMS-based MFA, YubiKeys does not rely on network connectivity and provides strong, passwordless authentication options for improved security and ease of use.
\nMulti-Factor Authentication is a critical component of modern cybersecurity. By requiring multiple verification steps, MFA enhances security, prevents data breaches, and provides an added layer of protection against cyber threats.
\nBusinesses should implement MFA by choosing the right multi-factor authentication provider to safeguard sensitive information, reduce fraud risks, and comply with security regulations.
\n1. Why is MFA important to security?
\nMFA is crucial to security because it adds an extra layer of protection by requiring multiple forms of verification, reducing the risk of unauthorized access.
\n2. What are the benefits of MFA security?
\nMFA security offers enhanced protection against cyber threats, mitigates the risk of stolen or weak passwords, and improves overall account security.
\n3. What is multi-factor authentication and why is it important to help prevent identity theft?
\nMulti-factor authentication (MFA) verifies user identity with multiple factors like passwords, tokens, or biometrics, reducing the risk of identity theft by ensuring only authorized users gain access.
\n4. What are the benefits of having an MFA?
\nHaving MFA provides improved security, reduced vulnerability to password-related attacks, increased trust with consumers, and compliance with security standards.
\n","frontmatter":{"date":"June 28, 2019","updated_date":null,"description":"In today’s digital landscape, cybersecurity threats are evolving rapidly. Businesses and individuals alike need stronger security measures to protect sensitive data. A highly effective method to improve security is through Multi-Factor Authentication (MFA). But what is multi factor authentication, and how does it work? Let’s dive into the details.","title":"What is Multi Factor Authentication (MFA) and How does it Work?","tags":["mfa","authentication","ciam solution","cx"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.4598540145985401,"src":"/static/bebdf0e50e1df0f97ff4169608b4f233/58556/mfa-cover.webp","srcSet":"/static/bebdf0e50e1df0f97ff4169608b4f233/61e93/mfa-cover.webp 200w,\n/static/bebdf0e50e1df0f97ff4169608b4f233/1f5c5/mfa-cover.webp 400w,\n/static/bebdf0e50e1df0f97ff4169608b4f233/58556/mfa-cover.webp 800w,\n/static/bebdf0e50e1df0f97ff4169608b4f233/cc834/mfa-cover.webp 1024w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.webp"}}}},{"node":{"excerpt":"It is hard to write 100% holes-free code, no matter how hard you try. Sometimes it is not even your own fault (language implementation…","fields":{"slug":"/engineering/3-simple-ways-to-secure-your-websites-applications/"},"html":"It is hard to write 100% holes-free code, no matter how hard you try. Sometimes it is not even your own fault (language implementation, server setups, etc.) and those factors are likely out of your control. That being said, as developers, we should strive to write our code as safe and secure as possible. Here are my suggestions to keep yourself from being woken up in the middle of the night:
\n1. DO NOT trust any user-input, PERIOD. Not even if it is yours truly. This is the most common attack vector for your web applications, whether it is just a contact form or an API end-point. For example, if a form is implemented to store data in a database, someone can try brute-forcing with classic SQL-injection techniques. Others can certainly try calling your API and see if there are any spotty error-handling issues. Sanitize all inputs as much as you can, and handle all errors behind the scenes properly and gracefully without exposing the actual details to the public.
\n2. UPDATE, UPGRADE and REPEAT. Chances are, a lot of your code is dependent on third-party libraries (open or closed source, does not matter). It is your job to make sure you are using the latest version for them all. When hackers find out you are using outdated or vulnerable code, you are done. I have seen this happening way too many times than I can count over the years when websites got hacked and outdated plugins or libraries was the main culprit.
\nYou might be saying, \"Hey, upgrading that library will break my code!!\". Well, what is your job again? Deal with it.
\n3. Web Application Firewall (WAF) Consider getting one if your server admin lets you, it can potentially save yourself a lot of embarrassments. Just keep in mind though it should not be your only security strategy, as WAFs will not stop all kinds of attacks. It is still your sole responsibility to write good code and repeat step 1 and 2.
\nHappyyyyy coding!
\n","frontmatter":{"date":"June 24, 2019","updated_date":null,"description":null,"title":"3 Simple Ways to Secure Your Websites/Applications","tags":["Engineering"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/5a3022253d6646c0ce3939c478b4481e/ad85c/hacker.webp","srcSet":"/static/5a3022253d6646c0ce3939c478b4481e/61e93/hacker.webp 200w,\n/static/5a3022253d6646c0ce3939c478b4481e/1f5c5/hacker.webp 400w,\n/static/5a3022253d6646c0ce3939c478b4481e/ad85c/hacker.webp 600w","sizes":"(max-width: 600px) 100vw, 600px"}}},"author":{"id":"Karl Wittig","github":null,"avatar":null}}}},{"node":{"excerpt":"Do you remember the Amazon outage that affected several high-profile customers back in 2011? On April 21st, widely-used sites such as Reddit…","fields":{"slug":"/engineering/failover-systems-and-loginradius-99-99-uptime/"},"html":"Do you remember the Amazon outage that affected several high-profile customers back in 2011? On April 21st, widely-used sites such as Reddit and Quora were brought down, and many others experienced latency or were knocked offline, too. Early that morning, as part of normal scaling activities, Amazon staff performed a network change. However, the change was done incorrectly and, after the staff attempted to correct it through a rollback, the inner mechanisms of the service made it unavailable to serve read and write requests. The ‘inner mechanisms’ responsible for the service unavailability are out of the scope of this article, but they are described in the service disruption summary that Amazon published. What interests us here is the strategies that companies can use to mitigate the negative effects on their products when a service they rely on fails. These strategies make up what is known as a failover system.
\nA failover system is a set of mechanisms that perform failover. In computer networking, failover is the process of switching to a redundant or standby server or network upon the abnormal termination of a previously-active server or network. The benefit of a failover system is obvious: with one in place, you can ensure your product or service will be available even when adverse events take place. Uptime—time during which a service is operational—is crucial to the success of your business. If your services are unavailable, you are likely to lose customers and any revenue they would have generated. In an article entitled ‘Lessons Netflix Learned from the AWS Outage,’ Netflix talks about the manual process they used to deal with the Amazon outage and acknowledges the importance of automating this process in the future so they can keep scaling their service. That is, the company acknowledges the importance of having an automated failover system in place instead of relying on a team of top engineers manually making changes every time there is an issue.
\nHow is an automated failover system set up? Let us consider the simplest scenario: setting a failover system for one server. By definition of a failover system, in addition to the main server, we need to have another redundant standby server that we can switch to whenever the main one fails. Since the redundant server must provide the same functionality as the first, it must be identical to it. Additionally, we need a tool that ensures client requests are routed to the redundant server in case of failure of the main one. We can achieve this by using a DNS failover tool. DNS is the internet protocol used to translate human-readable hostnames into IP addresses, and a DNS failover tool makes sure the “dictionary” (DNS tables) used for this translation are updated in the event of an outage. DNS failover tools know when to update the tables by periodically checking on the main server’s status. With these three tools—and some configuration—you can set up a simple, automated failover system. Of course, there are other considerations you must take when setting the failover system, such as ensuring the redundant standby server is hosted in a geographic area different from the main server’s location and using different companies to host your services. That way, your services will be less likely to go down simultaneously.
\nAt LoginRadius, we have set up automated failover systems in all layers of our architecture, which is why we can ensure 99.99% uptime on a monthly basis. With our services, you can be assured your customers will always be able to engage with your business, ensuring you will never lose these customers and any revenue they will generate.
\n","frontmatter":{"date":"June 24, 2019","updated_date":null,"description":null,"title":"Failover Systems and LoginRadius' 99.99% Uptime","tags":["Engineering","AWS"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.0050251256281406,"src":"/static/aa689bef0926b16dc0f50c38ca2e3f1c/18421/tech.webp","srcSet":"/static/aa689bef0926b16dc0f50c38ca2e3f1c/61e93/tech.webp 200w,\n/static/aa689bef0926b16dc0f50c38ca2e3f1c/1f5c5/tech.webp 400w,\n/static/aa689bef0926b16dc0f50c38ca2e3f1c/18421/tech.webp 719w","sizes":"(max-width: 719px) 100vw, 719px"}}},"author":{"id":"Ruben Gonzalez","github":"rubenprograms","avatar":null}}}},{"node":{"excerpt":"In January of 2019, Akamai acquired Janrain and rebranded their CIAM solution as “Identity Cloud,” a platform designed to improve security…","fields":{"slug":"/identity/best-janrain-alternative/"},"html":"In January of 2019, Akamai acquired Janrain and rebranded their CIAM solution as “Identity Cloud,” a platform designed to improve security access controls and identity management. Before the purchase price was revealed, Forrester predicted it would be in the $250M–$275M range (based on an estimation of Janrain’s annual revenue). In reality, the sale price was $125M—roughly half of Forrester’s estimate. Since then, perhaps in response to the Janrain acquisition, customers have reached out to LoginRadius seeking a Janrain alternative. Here’s what they told us.
\nLoginRadius has had many conversations with current and former Janrain customers in the last few months. Through these discussions, we’ve learned that the Janrain acquisition is playing out in a similar fashion to the Gigya acquisition. If you’re interested in reading about the pitfalls of the Gigya/SAP merger, you might like our article Looking for a Gigya Alternative?. In it, we explain some of the problems arising from the Gigya/SAP merger.
\nLikewise, in this article, I’ll demonstrate that while mergers and acquisitions (M&A) can be exciting, an acquisition may sometimes be damaging for customers, partners, and employees. To illustrate that, here are some of the reasons customers are seeking a Janrain alternative today.
\nOne of the chief concerns that companies have shared with us involves service level agreements (SLAs). In particular, we’ve heard that many companies fear that Akamai will not offer the flexibility of custom tech stacks. Their concern is that if they use software or apps not provided by Akamai, they’ll lose the quality, availability, and features that they relied on before the merger.
\nTo put it into perspective, former Gigya customers complained to us that during the SAP acquisition, they didn’t want to switch their tech stack to SAP. However, in order to get a full SLA and the optimal service and features they had come to expect, it suddenly became necessary.
\nThe reason for their cold feet is simple: switching software can lead to a massive drain of resources within large companies. Therefore, it’s reasonable for companies to avoid that kind of change. Let’s face it, if you already have a tried-and-true tech stack, wouldn’t you want to choose a CIAM solution that works with it?
\nAnytime a big acquisition or disruption occurs in a company, there’s a high probability that customer service may suffer. In fact, time and again, customers told our consultants that they switched from Akamai/Janrain or Gigya due to a decline in technical assistance and customer support.
\nAnother customer related complaint occurred after Akamai acquired Janrain. Janrain customers became concerned when their accounts did not auto-renew. Since the Janrain/Akamai merger, Akamai is exercising its right to renegotiate terms. As a result, Janrain customers are reported to be wary of the fine print on these new terms.
\nCustomers revealed that they noticed a lot of downtime on sites using Akamai Identity Cloud as their provider. Most recently, the NBA Finals game outage on Sportsnet created a lot of heat for Rogers. And since Janrain is the CIAM provider for Rogers, the outage is a result of their inability to handle peak loads. For any business that experiences surges in logins, downloads, or streaming, downtime can cost $300,000 (on average) in lost revenue.
\nKey Takeaway
\nAkamai is a security company, so its acquisition of Janrain confirms that CIAM is a security platform. Akamai clearly saw Janrain as a missing piece in their security company.
\nHowever, LoginRadius made this pivot sooner than Janrain—in 2016, to be precise. Simply put, we've spent more years innovating and delivering value to enterprises than Janrain has. Here are just some of the reasons why LoginRadius is the best Janrain alternative for your business.
\nOur 100% uptime is second to none.
\nYou don’t have to worry about surges or spikes driving customers away and hurting revenue. LoginRadius is the only identity platform with a 100% uptime.
\nWe’re a global leader in customer identity.
\nLoginRadius was named a global CIAM leader by KuppingerCole and has been positioned ahead of other vendors such as ForgeRock, Okta, and Ping Identity. Recently, LoginRadius received $17 million Series A funding, led by ForgePoint Capital and Microsoft. W__e may not be enterprise-size, but we’re enterprise grade—meaning you’ll get both dedicated service and an exceptional product from LoginRadius.
\nWe provide data privacy and consent solutions.
\nWe follow the strictest government regulations for privacy and consent and offer out-of-the-box solutions for GDPR, CCPA, and COPPA compliance. We also provide the highest industry standards for secure single sign-on, data storage, and customer access management.
\nWe’re 100% CIAM with 24/7 tech support.
\nOur product consultants, customer support, and tech teams act quickly to meet your needs. Data migration from your current provider is included, as are customization features and fast deployment.
\nSimply put, LoginRadius excels at what Akamai/Janrain doesn’t—**giving companies an edge over the competition.**
\n“The secret to exceeding customer expectations
\nis knowing what customers want before they do.”
\nLoginRadius is a CIAM solution that offers seamless migration from your current provider within days. We also do migration testing on a staging site, so your customers won’t notice a thing.
\nWant to hear more about making the switch to LoginRadius? Call a LoginRadius digital identity consultant today at 1-844-625-8889. We’ll be happy to give you a product demo so you can compare LoginRadius with your current provider.
\n![\"Janrain](\"/23b2208278dbd4fe5b7ddff1307ce0b5/CTA-Graphics-for-Blogs-V02.01-15.webp\")
Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards and refining approaches to building secure, seamless experiences.
\nWe’re here to support developers on that journey. We know how important simplicity, efficiency, and well-structured documentation are when working with identity and access management solutions. That’s why we’ve redesigned the LoginRadius website—to be faster, more intuitive, and developer-first in every way.
\nThe goal? Having them spend less time searching and more time building.
\nLoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.
\nHere’s a closer look at what’s new and why it’s important:
\n![\"This](\"/f46881583c7518a93bb24e94c32320de/a-developer-friendly-dark-theme.webp\")
Developers spend long hours working in dark-themed IDEs and terminals, so we’ve designed the LoginRadius experience to be developer-friendly and align with that preference.
\nThe new dark mode reduces eye strain, enhances readability, and provides a seamless transition between a coding environment and our platform. Our new design features a clean, modern aesthetic with a consistent color scheme and Barlow typography, ensuring better readability. High-quality graphics and icons are thoughtfully placed to enhance the content without adding visual clutter.
\nSo, whether you’re navigating our API docs or configuring authentication into your system, our improved interface will make those extended development hours more comfortable and efficient.
\n![\"This](\"/e5358b82be414940f3fb146013845933/capabilities.webp\")
We’ve restructured our website to provide a straightforward breakdown of our customer identity and access management platform capabilities, helping you quickly find what you need:
\nThis structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.
\n![\"This](\"/a8c155c2b6faf3d5f4b4de4e2b14d763/developers-menu.webp\")
We’ve been analyzing developer workflows to identify how you access key resources. That’s why we redesigned our navigation with one goal in mind: to reduce clicks and make essential resources readily available.
\nThe new LoginRadius structure puts APIs, SDKs, and integration guides right at the menu bar under the Developers dropdown so you can get started faster. Our Products, Solutions, and Customer Services are also clearly categorized, helping development teams quickly find the right tools and make informed decisions.
\n![\"This](\"/b2f9a964a2da0ea83e2f8596b833bba7/we-support-your-tech-stack.webp\")
Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.
\nOur platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.
\nCheck out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.
\nDo not forget to explore the improved navigation and API documentation, and get started with our free trial today. We’re excited to see what you’ll build with LoginRadius!
\n","frontmatter":{"date":"February 21, 2025","updated_date":null,"description":"LoginRadius’ vision is to give developers a product that simplifies identity management so they can focus on building, deploying, and scaling their applications. To enhance this experience, we’ve redesigned our website interface, making navigation more intuitive and reassuring that essential resources are easily accessible.","title":"Revamped & Ready: Introducing the New Developer-First LoginRadius Website","tags":["Developer tools","API","Identity Management","User Authentication"],"pinned":true,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7857142857142858,"src":"/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp","srcSet":"/static/80b4e4fbe176a10a327d273504607f32/61e93/hero-section.webp 200w,\n/static/80b4e4fbe176a10a327d273504607f32/1f5c5/hero-section.webp 400w,\n/static/80b4e4fbe176a10a327d273504607f32/58556/hero-section.webp 800w,\n/static/80b4e4fbe176a10a327d273504607f32/99238/hero-section.webp 1200w,\n/static/80b4e4fbe176a10a327d273504607f32/7c22d/hero-section.webp 1600w,\n/static/80b4e4fbe176a10a327d273504607f32/1258b/hero-section.webp 2732w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.webp"}}}},"pageContext":{"limit":6,"skip":846,"currentPage":142,"type":"///","numPages":164,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}