{"componentChunkName":"component---src-templates-blog-list-template-js","path":"/122","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"excerpt":"Programming is an excellent exercise for your brain as programmers deal with never-ending situations like bugs, compiler, issues, deadlines…","fields":{"slug":"/engineering/lets-take-meme-break/"},"html":"

Programming is an excellent exercise for your brain as programmers deal with never-ending situations like bugs, compiler, issues, deadlines, languages, etc. During all these times, other than the phenomenal codes, we produce MEMEs and a hell lot of MEMEs

\n

MEMEs can light the environment for every programmer in the world. On that note, there is a famous saying-

\n

“If debugging is the process of removing software bugs, then programming must be the process of putting them in – Edsger Dijkstra”

\n

Here is our developer picked list of 21 complied MEME for you:

\n

1. Always ready for new!!! - Kunal

\n

\n \n \n

\n

2. Nothing Changes With Time - Tanvi Jain

\n

\n \n \n

\n

3. Heaviest Object In The Universe - Nitesh Jain

\n

\n \n \n

\n

4. Perception!! - Vikram Jain

\n

\n \n \n

\n

6. I had a problem so I thought to use Java - Indrasen Kumar

\n

\n \n \n

\n

7. Avoid Handshakes. - Piyush Kumar

\n

\n \n \n

\n

8. I’m Really Unsure About My Own Creation - Kheenvraj Lomror

\n

\n \n \n

\n

10. Every IT Administrator. - Narendra Pareek

\n

\n \n \n

\n

12. My Logical Thinking as Programmer​​​. - Ankit Singh

\n

\n \n \n

\n

14. Programmers while Sleeping​. - Versha Gupta

\n

\n \n \n

\n

16. QA Life!! - Rakesh Pareek

\n

\n \n \n

\n

17. Infinite... - Hridayesh Sharma

\n

\n \n \n

\n

18. Python Lover!! - Aman Agrawal

\n

\n Vijay Singh Shekhawat\n

\n \n \n

\n

If you have better ones, reply in the comments below and we’ll include them.

\n","frontmatter":{"date":"September 04, 2020","updated_date":null,"description":null,"title":"Let’s Take A MEME Break!!!","tags":["MEME","Programming","Humor"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7241379310344827,"src":"/static/89b49574235e0c317d2219ca5e10b6d9/1c1a5/cover.png","srcSet":"/static/89b49574235e0c317d2219ca5e10b6d9/69585/cover.png 200w,\n/static/89b49574235e0c317d2219ca5e10b6d9/497c6/cover.png 400w,\n/static/89b49574235e0c317d2219ca5e10b6d9/1c1a5/cover.png 550w","sizes":"(max-width: 550px) 100vw, 550px"}}},"author":{"id":"Ashish Sharma","github":"ashish8947","avatar":null}}}},{"node":{"excerpt":"PKCE is an OAuth 2.0 security extension for public clients on mobile devices intended to avoid a malicious programme creeping into the same…","fields":{"slug":"/engineering/pkce/"},"html":"

PKCE is an OAuth 2.0 security extension for public clients on mobile devices intended to avoid a malicious programme creeping into the same computer from intercepting the authorisation code. The RFC 7636 introduction discusses the mechanisms of such an attack.

\n

PKCE has a different specification of its own. It allows applications to use the most reliable OAuth 2.0 flows in public or untrusted clients - the Authorization Code flow. In order to efficiently use a dynamically generated password, it achieves this by doing some setup work before the flow and some verification at the end of the flow.

\n

This is important because getting a fixed secret in a public client is not safe.

\n

In this blog, we will see how PKCE is useful in authorization code flow for OAuth and OIDC and how you can use this with your OAuth and OpenID Connect providers.

\n

What is PKCE

\n

Proof Key for Code Exchange as known as PKCE, is a key for preventing malicious attacks and securely performing code authorization flow.

\n

I would say, PKCE is used to provide one more security layer to the authorization code flow in OAuth and OpenID Connect.

\n

PKCE is mainly useful for the client-side application or any web apps that are using the client secret key and used to replace the static secret used in the authorization flow.

\n

This flow basically works with two parameters Code Verifier and Code challenge. Let's see what are these parameters, how we use them, and generate them.

\n

PKCE code verifier and challenge

\n

The code verifier is a cryptographically random string using the characters A-Z, a-z, 0-9, and the punctuation characters -._~ (hyphen, period, underscore, and tilde), between 43 and 128 characters long.\nOnce the client has generated the code verifier, it uses that to create the code challenge.

\n

For devices that can perform a SHA256 hash, the code challenge is a BASE64-URL-encoded string of the SHA256 hash of the code verifier.

\n

Generate code verifier and code challenge

\n

Here you can see the examples to generate the Code verifier and code challenge in different languages. Either you can find Node and Go Packages for this but I would recommend you to not depend on any package for such small things.

\n

NodeJs

\n
var crypto = require("crypto")\n\nfunction base64URLEncode(str) {\n    return str.toString('base64')\n        .replace(/\\+/g, '-')\n        .replace(/\\//g, '_')\n        .replace(/=/g, '');\n}\nvar verifier = base64URLEncode(crypto.randomBytes(32));\nconsole.log("code_verifier: ", verifier)\n\nif(verifier){\n    var challenge = base64URLEncode(sha256(verifier));\n    console.log("code_challenge: ",challenge)\n}\n\n\nfunction sha256(buffer) {\n    return crypto.createHash('sha256').update(buffer).digest();\n}
\n

Golang

\n
package main\n \nimport (\n    "crypto/sha256"\n    "encoding/base64"\n    "fmt"\n    "math/rand"\n    "strings"\n    "time"\n)\n \ntype CodeVerifier struct {\n    Value string\n}\n \nconst (\n    length = 32\n)\n \nfunc base64URLEncode(str []byte) string {\n    encoded := base64.StdEncoding.EncodeToString(str)\n    encoded = strings.Replace(encoded, "+", "-", -1)\n    encoded = strings.Replace(encoded, "/", "_", -1)\n    encoded = strings.Replace(encoded, "=", "", -1)\n    return encoded\n}\n \nfunc verifier() (*CodeVerifier, error) {\n    r := rand.New(rand.NewSource(time.Now().UnixNano()))\n    b := make([]byte, length, length)\n    for i := 0; i < length; i++ {\n        b[i] = byte(r.Intn(255))\n    }\n    return CreateCodeVerifierFromBytes(b)\n}\n \nfunc CreateCodeVerifierFromBytes(b []byte) (*CodeVerifier, error) {\n    return &CodeVerifier{\n        Value: base64URLEncode(b),\n    }, nil\n}\n \nfunc (v *CodeVerifier) CodeChallengeS256() string {\n    h := sha256.New()\n    h.Write([]byte(v.Value))\n    return base64URLEncode(h.Sum(nil))\n}\n \nfunc main() {\n    verifier, _ := verifier()\n    fmt.Println("code_verifier: ", verifier.Value)\n    challenge := verifier.CodeChallengeS256()\n    fmt.Println("code_challenge :", challenge)\n}\n
\n

Implement the OAuth 2.0 Authorization Code with PKCE Flow

\n

Get the Authorization code

\n

In the OAuth Authorization flow, we need to have the code verifier and code challenge to start with the authentication and obviously an OAuth provider to connect.

\n

For the initial request, we need to pass the codechallenge and codechallenge_method to the OAuth or OIDC provider that supports PKCE based flow.

\n

The request will look like:

\n
Provider + /oauth/redirect?\nclient_id={client_id}\n&redirect_uri={Callback URL}\n&scope={Scope}\n&response_type=code\n&state={random long string}\n&code_challenge={code challenge}\n&code_challenge_method=SHA256
\n

The provider should redirect you to the authentication/login page and where you’ll get the code after successful authentication.

\n

Code Exchange

\n

In the code exchange request, we need to pass the code we have received through the above request and the code verifier that we have generated in our first step.

\n
POST Provider + /oauth/access_token\n\nRequest body:\n{\n   client_id:{client_id},\n   client_secret:{client_secret},\n   redirect_uri:{redirect_uri},\n   response_type:token,\n   Code:{code} // That we have received in authorization request\n   code_verifier: {code verifier // generated in the first step\n}
\n

Once the codeverificer hash matches with the codechallenge of the authorization request, You will get the token in the response with status code 200 OK.

\n
{\n    "access_token": "c5a****b-****-4*7f-a********e4a",\n    "token_type": "access_token",\n    "refresh_token": "5*****82-b***-**82-8c*1-*******7ce",\n    "expires_in": 11972\n}
\n

That's it and you've implemented PKCE flow in your application.

\n","frontmatter":{"date":"September 03, 2020","updated_date":null,"description":"If you are working with OAuth and OIDC authorization code flow and want to setup PKCE flow then this article will help you to understand everything about PKCE.","title":"PKCE: What it is and how to use it with OAuth 2.0","tags":["PKCE","Oauth","OIDC"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/7ba5011bcf44e895dd050e8766d4d005/2a4de/pkce.png","srcSet":"/static/7ba5011bcf44e895dd050e8766d4d005/69585/pkce.png 200w,\n/static/7ba5011bcf44e895dd050e8766d4d005/497c6/pkce.png 400w,\n/static/7ba5011bcf44e895dd050e8766d4d005/2a4de/pkce.png 600w","sizes":"(max-width: 600px) 100vw, 600px"}}},"author":{"id":"Narendra Pareek","github":"pareek-narendra","avatar":null}}}},{"node":{"excerpt":"Single-page applications, or SPAs, are web applications that load a single HTML page and update it by dynamically rendering the browser's…","fields":{"slug":"/identity/single-page-applications/"},"html":"

Single-page applications, or SPAs, are web applications that load a single HTML page and update it by dynamically rendering the browser's information as (and when) a user interacts with the app.

\n

The loading mechanism of SPAs is different from traditional page loads where the server had to re-render the entire webpage with every click and send it back to the browser—making the process time-consuming.

\n

Today, with a new breed of users who expect data to be available instantly and accessible everywhere, developers use JavaScript libraries and tools like Jquery, Angular to create single, responsive HTML pages. Such pages can be broken down into smaller sections, and the JavaScript code running on the web browser calls the required APIs on a server that returns the data.

\n

Advantages..?

\n

Well, Single-Page Applications make users' experience incredibly engaging and unique. The \"bits and pieces\" methodology makes load time much faster and fluid for users. Also, because the amount of information a server has to send back is a lot less, the application becomes cost-effective. 

\n

Examples of Single-Page Application 

\n

A classic example of single-page applications is Gmail. They have mastered SPA-approach. You may notice that we do not generally need to refresh Gmail when a new email comes; we are notified instantly. It's obviously communicating with the server, but the JavaScript code hides the inbox and brings the message body on the same screen. 

\n

Other notable examples of Single-Page Applications include: 

\n\n

Advantages of Single-Page Applications

\n

According to Google's research, every time a page load goes from 1 sec to 3 sec, the probability of bounce rate increases by 32%. For 10 sec, the chance rises to a whopping 123%. 

\n

No matter what, faster's always better.

\n

One of the major benefits of single-page applications is velocity. The majority of the resources that SPAs need—viz.HTML, CSS, and Scripts are loaded along with the application. They don't need to be reloaded throughout the entire session. 

\n

Data is the only entity that is oscillated between the server and the webpage. This makes the application efficient and incredibly responsive to any query. 

\n

From the business perspective 

\n

Fast and responsive: Probably by now, that's a given. With SPAs, businesses can increase the loading speed of their webpages significantly. Because they only reload content requests asked by the user, the server load is much lighter. It is, in fact, half of the server load compared to multi-page applications.

\n

Better cache capabilities: Another advantage of single-page applications is that it can cache local data with utmost precision. It only takes one request to a server, and single-page applications effectively store all the data it receives. In the event of loss internet, this data can be put to use for seamless operation. 

\n

Frictionless user experience: If you are planning to build a single-page web application, rest assured, you will be offering frictionless user experiences to your consumers. Since it only loads the requested data, there is a significant improvement in performance as well. 

\n

From the consumer perspective 

\n

Speaking from the consumers' end, the apparent advantages of exposing them to single-page websites is the speed and ability to work with no connectivity. 

\n

These applications offer continuous user experiences, meaning they are easy to explore. In addition, when businesses add options like parallax scrolling and transitions to the picture, they make the customer journey even better.

\n

Single-page applications can be the best bet for mobile users too. Users spend most of the time scrolling feeds on Facebook and Instagram. They can sit back, relax, and enjoy the show.

\n

\n cybercriminals a broader scope for attack.

\n

Other common security issues include:

\n

Authentication and Session Tracking

\n

Usually, browsers that run in single-page applications interact with two different systems- 

\n\n

In some instances, web server sessions protect the APIs behind a single page application, but this means that all business APIs should be proxied by a web server. That typically involves session cookies which are quite vulnerable to cyber attacks.

\n

Cross-Site Request Forgery (CSRF)

\n

CSRF or XSRF, or sea-surfing is one of the oldest web application attacks. Usually, CSRFs are performed through social engineering, for example, via forged emails or links that fool the user into sending a fake request to the server.

\n

It happens when a malicious website has a link that connects to another website that the user has already signed in to. The bad actors authenticate the unaware user, so it is nearly impossible to distinguish a legitimate request from a fake one. 

\n

Here's an instance of how a CSRF can take place:

\n\n

Securing Single-Page Applications with LoginRadius

\n

\n \n \n

\n

Now the questions arise, how do you safely authorize and authenticate your Single Page (SPA) users? Here, we are being particular about JavaScript web applications that run on the same domain as the API.

\n

LoginRadius offers two options to cope up with the cybersecurity-related shortcomings. 

\n\n

Federated SSO

\n

LoginRadius uses popular token-based protocols like OAuth2 and OpenID Connect for federated logins. Examples include Login with Facebook, Google, or any other third-party sites.

\n

Unlike the older SAML 2.0, which could be used only once as proof of identity, these new protocols can be used over and over again to access protected API resources. 

\n

OAuth 2.0: OAuth2 is an industry-standard protocol for token-based authentication and authorization. It supports multiple grant types, which means users can grant access to their resources from one application to another without exposing their credentials, every time.

\n

It functions by giving short-lived access tokens to the Single-Page Application, which in turn authorizes the SPA so it can access the protected API services. It is often conducted on behalf of the logged-in user.

\n

OpenID Connect: LoginRadius also supports standard OpenID Connect, which is an identity layer on top of the OAuth 2.0 protocol. It is used to verify user identity depending on the authentication performed by an Authorization Server. With OpenID Connect, you can also retrieve basic profile information about the user.

\n

Web SSO

\n

Web SSO is browser-based session management that uses cookies to manage sessions between applications. Cookies are created by the server and contain information that a browser sends to the server on request. LoginRadius IDX uses a centralized domain to perform the authentication and, when requested, shares the session with authorized applications.

\n

It helps users log into multiple applications, irrespective of the platform or domain, provided they are logged in to one application in the first place. 

\n

Conclusion 

\n

Cybersecurity issues aren't unique to Single-Page Applications. The users make requests and not JavaScript. Also, the result is produced in HTML and not in JSON or any other format. 

\n

Unlike the traditional non-SPAs where you had to secure individual pages on the server, all you need is to secure the data endpoints in single-page applications. Going by the options above, dodging cybercriminals should not be a big deal.

\n

\n \n \n

\n","frontmatter":{"date":"September 03, 2020","updated_date":null,"description":"Single-page apps, or SPAs, are web applications that load and update a single HTML page by dynamically rendering details from the browser as (and when) a user interacts with the programme.","title":"Single-Page Applications: Building A Secure Login Pathway with LoginRadius","tags":["cx","authentication","ciam solution"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/a795dd7ad68a55baf8f9f906014d1c75/33aa5/single-page-applications.jpg","srcSet":"/static/a795dd7ad68a55baf8f9f906014d1c75/f836f/single-page-applications.jpg 200w,\n/static/a795dd7ad68a55baf8f9f906014d1c75/2244e/single-page-applications.jpg 400w,\n/static/a795dd7ad68a55baf8f9f906014d1c75/33aa5/single-page-applications.jpg 768w","sizes":"(max-width: 768px) 100vw, 768px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.jpg"}}}},{"node":{"excerpt":"Big Data - Introduction Earlier, we were only dealing with well-structured data, hosted in large data warehouses, and investing a cost in…","fields":{"slug":"/engineering/big-data-testing-strategy/"},"html":"

Big Data - Introduction

\n

Earlier, we were only dealing with well-structured data, hosted in large data warehouses, and investing a cost in maintaining those data warehouses and hiring expert professional to maintain and secure information hosted in that data warehouse. Data was structured and can be queried anything as per the needs. But now, this exponential growth of data generates a new vision for data science along with some major challenges.

\n

Big Data is something which is growing exponentially with time, and carry raw but very valuable information inside that can change the future of any enterprise. It is a collection, which represents a large dataset, may be collected from multiple sources, or stored in an organization.\nLet‟s understand a real-time example, Big companies like Ikea and Amazon are leveraging the benefit of big data by collecting data from customer‟s buying patterns at their stores, their internal stock information, and their inventory demand-supply relations and analyze all, in seconds even in real-time to add value to its customer experience.

\n

So, extracting information from a large dataset somewhat calls a concept of Data mining which is an analytic process originally designed to explore large datasets. The ultimate goal of data mining is to search for consistency in a pattern or systematic relationship between variables, which helps in predicting the next pattern or behavior.

\n

Now, if we take concepts of data mining forward along with large data set, to some extent it becomes a blocker for our existing approach, because big data may contain structured or unstructured data even it may contain data in multiple formats also.

\n

Big Data Testing

\n

Testing is an art of achieving quality in your software product, in terms of perfection of functionality, performance, user experience, or usability. But for big data testing, you need to keep your focus more on the functional and performance aspects of an application. Performance is the key parameter in any big data application which is meant to process terabytes of data. Successful processing of terabytes of data using a commodity cluster with a number of other supportive components needs to be verified. Processing should be faster and accurate which demands a high level of testing.

\n

Processing may be of three types:–

\n

\n \n \n

\n

And based on which, we need to integrate different components along with NoSQL data store as per the needs.

\n

Big Data Testing - Test Data

\n

Data plays a vital role in the testing of big data applications. Application is meant to process data and provide an expected output based on implemented logic. The logic needs to be verified before moving to production, as the implementation of logic is completely based on business requirements and data.

\n

1. Test Data Quality

\n

Good quality test data is as important as the test environment. In the big data world, data can have any format or size, it may be in the form of a document, XML, JSON, PDF, etc. at the same time data size may go up to terabytes of petabytes. Hence, test data should also have multiple formats and size should be large enough to ensure the handling of large data processing. In big data testing, it needs data with logical values as per the application requirement and format which is supported by the application.

\n

Along with it, data quality is another aspect of big data testing. Ensuring the quality of data before processing through application ensures the accuracy of the final output. Data quality testing itself is a huge domain and covers a lot of best practices which include – data completeness, conformity, accuracy, validity, duplication, and consistency, etc. It should be included in the big data testing and this ensures the level of accuracy application is supposed to provide.

\n

2. Test Data Generation

\n

The generation of test data is again a challenging job, there are multiple parameters, which have to be taken care of while generating test data. It needs a tool, which can help to generate data and should have functions or logic can also be applied over it. Tools like Talend (an open studio) is the best candidate to fulfill the requirements of data generation.

\n

3. Data Storage

\n

After the generation of test data along with quality, it needs to host on a file system. For testing big data applications, data should be stored in the system similar to the production environment. As we are working in big data space, there should have a different number of nodes, and data must be in a distributed environment.

\n

Big Data Testing - Test Environment

\n

In Big data testing, the test environment should be efficient enough to process a large amount of data as done in the case of a production environment. Real-time production environment clusters generally have 30-40 nodes of cluster and data is distributed on the cluster nodes. There must have some minimum configuration for each node used in the cluster. A cluster may have two modes, in-premise or cloud. For testing in big data, it needs the same kind of environment with some minimum configuration of node.

\n

Scalability is also desired to be there in the test environment of big data testing, it helps to study the performance of application with the increase in the number of resources. That data can be used to define SLA (service level agreement) for that particular application.

\n

Big Data Testing can be categorized into three stages:

\n

\n \n \n

\n

Step 1: Data Staging Validation

\n

The first stage of big data testing, also known as a Pre-Hadoop stage, is comprised of process validation.

\n
    \n
  1. Validation of data is very important so that the data collected from various source like RDBMS, weblogs, etc are verified and then added to the system.
    2. \n
  2. To ensure data match you should compare source data with the data added to the Hadoop system.
    3. \n
  3. Make sure that the right data is taken out and loaded into the accurate HDFS location
    4. \n
\n

Step 2: “Map Reduce” Validation

\n

Validation of “Map Reduce” is the second stage. Business logic validation on every node is performed by the tester. Post that authentication is done by running them against multiple nodes, to make sure that the:

\n\n

Step 3: Output Validation Phase

\n

The output validation process is the final or third stage involved in big data testing. The output data files are created and they are ready to be moved to an EDW (Enterprise Data Warehouse) or any other such system as per requirements. The third stage consisted of:

\n\n

Big Data - Performance Testing

\n

Big data applications are meant to process a large amount of data, and it is expected that it should take minimum time to process maximum data. Along with it, application jobs should consume a considerable amount of memory and CPU. In big data testing, performance parameter plays an important role and helps to define SLA's. It covers the performance of the base machine and cluster. Also, for example, In the case of Hadoop, map-reduce jobs should be written with proper coding guidelines, to perform better in the production environment. Profiling can also be done on map-reduce jobs before integration, to ensure their optimized execution.

\n

Tools used in Big Data Scenarios

\n

\n \n \n

\n

Big Data Testing - Challenges

\n

In big data testing, certain challenges are involved which needs to be addressed by the big data testing approach.

\n

1. Test Data

\n

Exponential growth had been observed in the growth of data in the last few years. A huge amount of data are being generated daily and stored in large data centers or data marts. So, there is a demand for efficient storage and a way to process it in an optimized way. If we consider the telecom industry, it generates a large number of call logs daily and they need to be processed for better customer experience and compete in the market. The same goes with the test data, test data should be similar to production data and should contain all the logically acceptable fields in it.

\n

This becomes a challenge for testing big data application, generating test data similar to production data is a real challenge. Test data should also be large enough to verify proper working big data application.

\n

2. Environment

\n

The processing of data highly depends on the environment and its performance. An optimized environment setup gives high performance and fast data processing results. Distributed computing is used for the processing of big data which has data hosted in a distributed environment. The testing environment should have multiple numbers of nodes and data should be distributed over the nodes. At the same time, it also needs to monitor those nodes, to ensure the highest performance with minimum CPU and memory utilization. Nodes should be monitored and there should have a graphical presentation of node performance. So, the test environment has two aspects – distributed nodes and their monitoring, which should be covered in the testing approach.

\n

3. Performance

\n

Performance is the key requirement of any big data application, and of course because of which enterprises are moving towards NoSQL technologies, technologies that can handle their big data and process in the minimum time frame. A large dataset should be processed in a minimum considerable time frame. In big data testing, performance testing is a challenge, it requires monitoring of cluster nodes during execution and also time is taken for every iteration of execution.

\n

Conclusion

\n

Big Data is the trend that is revolutionizing society and its organizations due to the capabilities it provides to take advantage of a wide variety of data, in large volumes and with speed. Keeping the challenges in mind we have defined the approach of testing big data applications. This approach of big data testing will make it easy for a test engineer to verify and certify the business requirement implementations and for stack holders, it saves a huge amount of cost, which has to be invested to get the expected business returns.

\n","frontmatter":{"date":"September 02, 2020","updated_date":null,"description":"With the exponential growth in the number of big data applications in the world, Testing in big data applications is related to database, infrastructure and performance testing and functional testing. This blog guides what should be the strategy for testing Big Data applications.","title":"Big Data - Testing Strategy","tags":["Testing","Big Data","Big Data Testing"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/370acda0a8a364ef7098ce2df0537d12/ee604/big-data.png","srcSet":"/static/370acda0a8a364ef7098ce2df0537d12/69585/big-data.png 200w,\n/static/370acda0a8a364ef7098ce2df0537d12/497c6/big-data.png 400w,\n/static/370acda0a8a364ef7098ce2df0537d12/ee604/big-data.png 800w,\n/static/370acda0a8a364ef7098ce2df0537d12/f3583/big-data.png 1200w,\n/static/370acda0a8a364ef7098ce2df0537d12/5707d/big-data.png 1600w,\n/static/370acda0a8a364ef7098ce2df0537d12/eeb1b/big-data.png 1920w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Sudhey Sharma","github":"sudheysharma","avatar":null}}}},{"node":{"excerpt":"LoginRadius, a leader in cloud-based consumer identity and access management solution (CIAM) has released an industry report titled…","fields":{"slug":"/identity/loginradius-consumer-digital-identity-trend-report-2020/"},"html":"

LoginRadius, a leader in cloud-based consumer identity and access management solution (CIAM) has released an industry report titled \"Consumer Identity Trend 2020\" for C-suite professionals and product managers of B2C companies that deal with consumer‘s identity data.

\n

The learning objective for this industry analysis is to determine the opportunities and threats that exist within the identity environment.

\n

Report Overview

\n

The report offers a comprehensive overview of the Consumer Identity Trends of 2020. It aims to improve consumer experiences on a digital platform via extensive data analysis on consumer behavior and lifecycle.

\n

This research piece points out the increasing competition across all industry verticals and that consumer experience is a success key if businesses want to stand out in a highly competitive world.

\n

To achieve this, businesses need to identify their consumer behavior and pain points, including their preferred authentication methods, such as passwordless login or multi-factor authentication via email or SMS, or social sign-on.

\n

The data was collected from the LoginRadius Identity Platform, which serves and manages 1,17 billion consumer identities for thousands of websites and mobile applications. The research was conducted with data from 1 January 2019 until 10 May 2020.

\n

The key findings of the report have been outlined in the infographic below. It will help you understand:

\n\n

The report is available for download. Request your copy here.

\n

\n \n \n

\n","frontmatter":{"date":"September 02, 2020","updated_date":null,"description":"LoginRadius, a pioneer in cloud-based customer identity and access management (CIAM) solution, has released an industry report titled 'Consumer Identity Trend 2020' for C-suite professionals and B2C business product managers concerned with customer identity.","title":"LoginRadius Releases Consumer Digital Identity Trend Report 2020","tags":["industry news","consumer identity","digital identity"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.408450704225352,"src":"/static/7d9196cc2cfe81885fc3ca26265edec7/6051d/consumer-identity-report-loginradius.png","srcSet":"/static/7d9196cc2cfe81885fc3ca26265edec7/69585/consumer-identity-report-loginradius.png 200w,\n/static/7d9196cc2cfe81885fc3ca26265edec7/497c6/consumer-identity-report-loginradius.png 400w,\n/static/7d9196cc2cfe81885fc3ca26265edec7/6051d/consumer-identity-report-loginradius.png 769w","sizes":"(max-width: 769px) 100vw, 769px"}}},"author":{"id":"Rakesh Soni","github":"oyesoni","avatar":"rakesh-soni.jpg"}}}},{"node":{"excerpt":"Introduction Authentication is the necessary implementation for secure and genuine access to resources of web and mobile applications. It…","fields":{"slug":"/engineering/email-verification-api/"},"html":"

Introduction

\n

Authentication is the necessary implementation for secure and genuine access to resources of web and mobile applications. It helps to authorize the user and provide access control for applications based on the user’s credentials.

\n

There are various authentication mechanisms like Email, Phone numbers, Biometrics, etc. However, Email is still considered the primary means of authentication because other mechanisms are not as optimized or in approach to everyone.

\n

So it is safe to say that most of your application users used email for creating their accounts. With that, some users tend to use disposable email services for fake account creation. These fake accounts result in additional liability to your application resources and servers.

\n

You can effectively reduce such spams for your applications by analyzing the user’s email address during registration for the following aspects:

\n\n

There are some tools available that could help you analyze the above factors, and one such tool is EVA, an Email Verification API. It is a free API and analyzes the user’s email for all of the factors mentioned above.

\n

API Details

\n

The details of Email Verification API (API) is as follows:

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
ParametersValue
URLhttps://api.eva.pingutil.com/email
Query Param{ email: test@mail7.io }
Response{ \"status\": \"success\", \"data\": { \"email_address\": \"test@mail7.io\", \"domain\": \"mail7.io\", \"valid_syntax\": true, \"disposable\": true, \"deliverable\": true }}
\n

Valid_syntax, disposable, and deliverable are three attributes of this API, let’s see how these works:

\n

Output Parameters:

\n

valid_syntax\nThis attribute verifies the syntax of the entered email address matches the standard email address format or not. It is useful in the cases where the end-user might misspell email addresses while typing.

\n

disposable\nThis attribute verifies whether the entered email address domain belongs to the disposable email service. EVA checks the email address against a valid database of more than 4500 disposable email services. Thus, it can effectively help the developer to prevent users from registering using disposable email.

\n

deliverable\nThis attribute verifies whether the email domain has valid MX records or not. The email address is considered deliverable if the valid MX record for the email domain is found.

\n
\n

Note: A mail exchanger record (MX record) specifies the mail server responsible for accepting email messages on behalf of a domain name. It is a resource record in the Domain Name System (DNS).

\n
\n

The response received for the above three attributes of API can help you take further action. These attributes are not just limited to registration use cases, you can utilize them for other use cases like if you have an existing user base but would like to limit the spammers (who have registered using disposable emails) from commenting on the blog or accessing your application resources.

\n

This API tool has been developed and designed as a way of giving back to the developer community initiative by LoginRadius Developers. Your opinion is important to us. This way we can keep improving our product for the developer community. Please share your feedback here

\n","frontmatter":{"date":"August 31, 2020","updated_date":null,"description":"Email authentication, being the traditional way of authentication and used most widely. Increase in the spams has also increased the disposable email registrations. To reduce and identify such unwanted users, EVA(Email Verification API) is the tool, developed by LoginRadius developers.","title":"Email Verification API (EVA)","tags":["Free tool","Developer Resources ","Verification","Email"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/4991e427faf331bcbd24d1c66c1cad40/ee604/eva.png","srcSet":"/static/4991e427faf331bcbd24d1c66c1cad40/69585/eva.png 200w,\n/static/4991e427faf331bcbd24d1c66c1cad40/497c6/eva.png 400w,\n/static/4991e427faf331bcbd24d1c66c1cad40/ee604/eva.png 800w,\n/static/4991e427faf331bcbd24d1c66c1cad40/f3583/eva.png 1200w,\n/static/4991e427faf331bcbd24d1c66c1cad40/e4d72/eva.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Aman Agrawal","github":"aman-agrwl","avatar":null}}}}]},"markdownRemark":{"excerpt":"Identity is evolving, and developers are at the forefront of this transformation. Every day brings a new learning—adapting to new standards…","fields":{"slug":"/identity/developer-first-identity-provider-loginradius/"},"html":"

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.

\n

We’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.

\n

The goal? Having them spend less time searching and more time building.

\n

What’s New and Improved on the LoginRadius Website?

\n

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 spent the last few months redesigning our interface— making navigation more intuitive and reassuring that essential resources are easily accessible.

\n

Here’s a closer look at what’s new and why it’s important:

\n

A Developer-Friendly Dark Theme

\n

\"This

\n

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.

\n

The 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.

\n

So, 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

Clear Categorization for LoginRadius Capabilities

\n

\"This

\n

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:

\n\n

This structured layout ensures you can quickly understand each capability and how it integrates into your identity ecosystem.

\n

Developer-First Navigation

\n

\"This

\n

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.

\n

The 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

Quick Understanding of Integration Benefits

\n

\"This

\n

Developers now have a clear view of the tech stack available with LoginRadius, designed to support diverse business needs.

\n

Our platform offers pre-built SDKs for Node.js, Python, Java, and more, making CIAM integration seamless across popular programming languages and frameworks.

\n

Over to You Now!

\n

Check out our revamped LoginRadius website and see how the improved experience makes it easier to build, scale, and secure your applications.

\n

Do 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.jpg"}}}},"pageContext":{"limit":6,"skip":726,"currentPage":122,"type":"///","numPages":161,"pinned":"ee8a4479-3471-53b1-bf62-d0d8dc3faaeb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}