Hi guys! When you write test cases, do you face the problem of sharing your test cases with your team members or having to use multiple colors for test cases?
\nI have a solution for these problems that is to maintain your test cases in an excel sheet.
Definition
\nTest cases are the part of testing by which a product can be tested properly according to a set of requirements.
Advantages of using test cases in excel sheets
\nStandard format of Test Cases
\nSome common fields that are used in test case writing are:
Test Case Id: This field is defined by what type of system we are testing. Below are the standard rules:
\nIn this way we can maintain all the test case IDs and if in the future we can get any requirement or change logs then easily add or change the test case using the following standard rules without changing the test case IDs of previously written test cases.
\nNote: Test Case Id always uses capital letters.
\nHere I have explained a very general format, this will cover almost all the scenarios but we can not assure that all the requirements have been covered, you can proceed the following way to cover all requirements.
\nKnowing that all the Requirements have been covered
\nTo know that all the requirements have been covered, you need to maintain a Traceability Matrix documentation. Let's take a look on how to create this document.
Traceability Matrix is a document which provides linking between the requirements and the product which we have developed.
\nTraceability Matrix can be divided into 2 parts:-
Summary :-\nThis section contains a summary of requirements like
\n1.1 Item: This field contains short descriptions of the items which will be tested.
\n1.2 Product Name: It contains the product name which you want to test.
\n1.3 Product Version: It contains the product version which you want to test.
\n1.4 Prerequisites: Prerequisites are the requirement of a system which are
\nneeded before we start testing. Prerequisites could be:
A certain action to be performed before execution steps are performed.
\nPrerequisites should be satisfied before the test case execution starts.
\n1.5 Change Prerequisites: Changes that were not necessary before but now are necessary for the system.
\n1.6 Exit Criteria: This field contains the requirements that must be fulfilled
\nin order to announce the completion of testing.
\n1.7 Test Summary: This field contains the status of the product: how many test
\ncases are passed, how many are failed, how many are on hold or how many are Invalid etc.
Traceability Matrix :
\nTraceability Matrix covers all the product requirements.We can say that it is a document which maps and traces requirements with test cases. Prime fields of this traceability matrix are
\n2.1 Requirement Id: This field identifies all the testable requirements.
\n2.2 Requirement Description: This field contains the short
\ndescription of requirements.
\n2.3 Test Case Id: According to requirements description which test case id is
\ncovered.
\n2.4 Status: Mention here the status of test cases such as passed, failed, on hold or
\ninvalid.
As per the image below:
\nURL : your-site-domain/admin/login All above steps are used to show admin login page. But if you want that only administrator can login through page admin/login then follow the following the next steps. Note: If you want that administrator can’t login through user login page then add following code to do this. Add the mentioned code in function yourmodule_external_validate Complete code of function yourmodule_external_validate looks like: If you are searching over the web and can’t find anything to create separate admin login page in drupal, Please follow the mentioned above steps and you are done. Also create different layout for this admin login page. This tutorial provides a solution to get email alerts, when a unhandled error occurs. For this tutorial, we are using WordPress. Imagine you created a php application and it’s running fine. A couple of days later, a user complains about an error which you’re totally unaware of. Such unhandled errors are very common in php applications. So, to find these issues, we are going to send email notifications whenever an error occurs. Step 1. First of all we need to identify a common application file that include at top of application. in this case the file is “wp-config.php” at the root of your wordpress hosting directory. Step 2. Let’s add the following line of code in this file under php tag. Step 3. Now save the file and upload on server. Whenever we got any error in wordpress then above code will send an email to given email-address (example@example.com). You can use the above code on production websites to improve application performance and track all errors that’s are missed. Similarly we can use above code in drupal, joomla, and many other content management systems. So last week while I was setting the analyzers on ElasticSearch settings for Email field, it took me some good time to find the perfect custom analyzer for my purpose, so I feel it might be useful to share this with someone who needs it. When a document is indexed, its individual fields are subject to the analyzing and tokenizing filters that can transform and normalize the data in the fields. For example — removing blank spaces, removing html code, stemming, removing a particular character and replacing it with another. At indexing time as well as at query time you may need to do some of the above or similiar operations. For example, you might perform a Soundex transformation (a type of phonic hashing) on a string to enable a search based upon the word and upon its 'sound-alikes'. Let me briefly explain what I am trying to do with my Email field. The email addresses will be stored as a comma separated string with potentially multiple email addresses, and what I am expecting is after the to search to retrieve the matching results. Besides the exact match like search for Here is the full schema for it: And the search schema is: If you decide to keep reading, then it means you have the same needs as I did so I hope the following solution can actually help. This setting will perfectly address the issues from above, and do not generate way to much tokens in your ES cluster. Integrating social into your site can drastically improve user engagement with your platform. Below are a few useful solutions and implementation instructions. Social Login, also known as Social Sign On, Allows you to bypass traditional registration forms and utilize the systems in place by social providers in order to retrieve a copy of the users data and a unique identifier for the user that can be used to identify that user in your system. The following guides go over setting up Social Login with a few common Social Providers: Most major social providers offer an easy tool to formulate and include sharing buttons on your pages. Below is an example of setting up an easy to use social sharing button with Facebook: Next include the div that will contain the sharing button on your page with the following data attributes: Sample Div: You can find information on generating sharing links with other providers in the following locations: Or you can contribute to our open source project on github- Github-Social9 Follow buttons work very much the same as the social sharing buttons above. Simply include the relevant SDK and div with some customizations and users will be able to follow(and un-follow) your brand directly from your page. Below is an example of setting up a Twitter follow button: You can set the data attributes in the above link to control various aspects of the follow button. Find information on generating follow buttons for other social providers in the following locations: One of the most common and easy to configure social integrations is setting up links to your companies Social profiles. You can improve upon this by utilizing one of the Social providers branded icons to better display the linking UX. Get a copy of Facebooks Branded Icon. Now that you have setup the above social features your users will have a variety of touch-points to keep them active and interacting with your site, seamlessly driving user conversions and making brand ambassadors of your users. Introduction Authentication and authorization both are most important things for any system and application. This blog starts with authentication and authorization concepts and after that explains the three default important ways and three custom authentication ways for doing authentication and authorization i.e. windows, forms ,passport, multipass, JWT and SAML authentication. Plus, in this blog I will explain some fundamental concepts about the different authentication system. Authentication and Authorization Authentication is the process for checking the identity of a user based on the user’s credentials. Generally, user’s credentials are in the form of user ID and password, and we check their credentials from database or equivalent alternative, if it exists then user is a valid candidate for next process - authorization. Authorization also known as “Permission Control” will come after authentication. Authorization is the process of deciding what kind of resource a user can access based on their identity and checking whether the authenticated user has sufficient rights to access the requested resources. Typically a resource can be an ASP.NET web page, media files (MP4, GIF, JPEG etc), compressed file (ZIP, RAR) etc. ASP.NET default authentication Providers 1. Form Authentication Normally, form authentication is based on cookies, the authentication and permission settings are stored in cookies. However, we can also use form authentication without cookies, and in cookie-less form authentication we can use query string for passing user details. Remember, the key concept is always ONLY allow the user with correct credential also enough permission to view certain resources, so we need to capture their information and compare with what we have stored in the database. And no matter what kind of form authentication we use, after we receive the data on server end, we will compare them with the data stored in any storage method/provider. For example, we can store username and password in the web.config file, a JSON file, or a database table. Forms authentication flow: 2. Passport Authentication Passport authentication is a centralized authentication service provided by Microsoft. The .NET Passport single sign-in service. When we use passport authentication then user authentication in your application is managed by Microsoft's passport service. Passport authentication uses encrypted cookies to manage the authentication. How Password authentication works Users do not need to retype their sign-in name and password when moving from site to site. Those .NET Passport–enabled sites will issue a set of encrypted cookies in the .NET Passport central servers' domain to facilitate silent and seamless sign-in across sites. In some cases, sites owners will first redirect their end-users to .NET Passport sign-in and to authenticate upon first viewing of their site. If the users are logged in already, they'll get authenticated by ASP.NET, and if they are not logged in they will get redirected to passport servers (i.e hotmail, Live etc.) to login first. If user successfully authenticates himself, it will return a token to your website. 3. Windows Authentication We use windows authentication when we are creating a web application for a limited number of users who already have Windows account and this type of authentication is quite useful in an intranet environment. This authentication method uses local users windows account 'credentials' for to validate the user. Dot Net web application generally hosted on IIS(Internet Information Server) so the requests go directly to IIS to provide the authentication process in a Windows-based authentication model. The entire responsibility of authentication is done by IIS. It first takes the user’s credentials from the domain login. If this process fails, IIS displays an alert dialog box so the user can enter or re-enter his login information. Windows authentication have some advantages and disadvantages: Windows authentication Advantage Windows authentication dis-Advantage 4. Custom authentication Provider Multipass authentication is a single sign on authentication. Suppose you have multiple sites and you want to create a single account for a user on both sites then you can use Single Sign-On. Single Sign-On is authentication system it allow user to share his authentication details with your there site. This allows a seamless experience for your users without forcing them to create a separate account on your second site. A multipass is simply a hash of keys and values, provided as an AES encrypted JSON hash. JWTs represent a set of claims as a JSON object that is encoded in a JWS and/or JWE structure. This JSON object is called “JWT Claims Set”. The JSON object consists of zero or more name/value pairs (or members), where the names are strings and the values are arbitrary JSON values. These members are the claims represented by the JWT. Your JWTs can contain any information you want; the user's name, birthdate, email, etc. You do this with claims based authorization. You then just tell your provider to make a JWT with these claims from the claims principle. SAML - Security Assertion Markup Language SAML. SAML is developed by the Security Services Technical Committee of \"Organization for the Advancement of Structured Information Standards\" (OASIS). SAML is an XML-based framework for exchanging user authentication. The purpose of SAML is to enable Single Sign-On for web applications across various domains. SAML have three components: assertions, protocol, and binding. Assertions are authentication, attribute, and authorization. Authentication assertion validates the user's identity. Attribute assertion contains specific information about the user. And authorization assertion identifies user role and permissions. SAML works with multiple protocols including Hypertext Transfer Protocol (HTTP), Simple Mail Transfer Protocol (SMTP), File Transfer Protocol (FTP) and also supports SOAP Summary Different authentication methods are available, and website’s owner always gets confused about which authentication method they should use, here I have explained some of the popular authentication and authorization methods, hope it made it a little bit clear for you. And I will provide some in-depth details about each type of authentication in my next blog, happy coding. Google has prepared a roadmap to restrict third-party cookies in Chrome. Since 04 January 2024, Chrome has rolled out third-party cookie restrictions for 1% of stable clients and 20% of Canary, Dev, and Beta clients. What does it mean for user authentication? On one hand, Google believes third-party cookies are widely used for cross-site tracking, greatly affecting user privacy. Hence, Google wants to phase out (or restrict) supporting third-party cookies in Chrome by early Q2 2025 (subject to regulatory processes). On the other hand, Google introduced Privacy Sandbox to support the use cases (other than cross-site tracking and advertising) previously implemented using third-party cookies. In this article, we’ll discuss: Third-party cookie restrictions affect user authentication in three ways, as follows. If your website or app uses an external Identity Provider (IdP) — like LoginRadius, the IdP sets a third-party cookie when the user authenticates on your app. If you have multiple apps across domains within your organization and authentication is handled using an IdP (internal or external) with web SSO, you already use third-party cookies to facilitate seamless access for each user using a single set of credentials. If you have implemented web SSO with one primary domain and multiple sub-domains of the primary domain, third-party cookie restrictions may not apply. For now, Google doesn’t consider the cookies set by sub-domains as third-party cookies, although this stance may change in the future. For example, you have apps at Federated SSO is similar to, albeit different from, web SSO. It can handle multiple IdPs and applications—aka., Service Providers (SPs)—spanning multiple organizations. It can also implement authentication scenarios that are usually implemented through web SSO. Usually, authentication is handled on a separate pop-up or page when the user wants to authenticate rather than on the application or website a user visits. For example, you already use federated SSO if you facilitate authentication for a set of apps through multiple social identity providers as well as traditional usernames and passwords. Note: It is also possible to store tokens locally, not within cookies. In this case, third-party cookie restrictions won’t affect token-based authentication. However, the restrictions still affect authentication where tokens are stored within third-party cookies (a common and secure method). Google has been developing alternative features and capabilities for Chrome to replace third-party cookies as part of its Privacy Sandbox for Web initiative. Specific to authentication, Google recommends the following: CHIPS are a restricted way of setting third-party cookies on a top-level site without making them accessible on other top-level sites. Thus, they limit cross-site tracking and enable specific cross-site functionalities, such as maps, chat, and payment embeds. For example, a user visits If the user visits You should specifically opt for partitioned cookies (CHIPS), which are set with partitioned and secure cookie attributes. If you’re using an external identity provider for your application, CHIPS is a good option to supplant third-party cookie restrictions. However, CHIPS may not be ideal if you have a web SSO or federated SSO implementation. It creates separate partitioned cookies for each application with a separate domain, which can increase complexity and create compatibility issues. With Storage Access API, you can access the local storage in a third-party context through iframes, similar to when users visit it as a top-level site in a first-party context. That is, it gives access to unpartitioned cookies and storage. Storage Access API requires explicit user approval to grant access, similar to locations, camera, and microphone permissions. If the user denies access, unpartitioned cookies and storage won’t be accessible in a third-party context. It is most suitable when loading cross-site resources and interactions, such as: Verifying user sessions when allowing interactions on an embedded social post or providing personalization for an embedded video.\nEmbedded documents requiring user verification status to be accessible. As it requires explicit user approval, it is advisable to use Storage Access API when you can’t implement an identity use case with the other options. With Related Website Sets, you can declare a Chrome automatically recognizes related website sets declared, accepted, and maintained in this open-source GitHub repository: Related Website Sets It provides access through Storage Access API directly without prompting for user approval, but only after the user interacts with the relevant iframe. It is important to declare a limited number of domains in related website sets that are meaningful and used for specific purposes. Google may block or suspend any exploitative use of this feature. The top-level site can also request approval for specific cross-site resources and scripts to Storage Access API using If you’re using an external identity provider for your web application, you can declare the domain of the identity provider in the related set to ensure limited third-party cookies and storage access to the identity provider, thus ensuring seamless user authentication. Related Website Sets can also work to supplement third-party cookie restrictions in web SSO and federated SSO if the number of web applications (or domains) is limited. FedCM API enables federated SSO without third-party cookies. With FedCM API, a user follows these steps for authentication: You can access a user demo of FedCM here: FedCM. For more information about implementing federated SSO with FedCM API, go through the FedCM developer guide. Firstly, we’re committed to solving our customers' user identity pain points — and preparing for the third-party cookies phase-out is no different. We’ll implement the most relevant and widely useful solutions to facilitate a smooth transition for our customers. Please subscribe to our blog for more information. We’ll update you on how we help with the third-party cookie phase-out. The proposed changes to phase out third-party cookies and suggested alternatives are evolving as Google has been actively collaborating and discussing changes with the border community. Moreover, browsers like Firefox, Safari, and Edge may approach restricting third-party cookies differently than Google does. From LoginRadius, we’ll keep you updated on what we’re doing as a leading Customer Identity and Access Management (CIAM) vendor to prepare for the third-party cookie phase-out. Top-level site: It is the primary site a user has visited. First-party cookie: A cookie set by the top-level site. Third-party cookie: A cookie set by a domain other than the top-level site. For example, let’s assume that a user has visited \n
\n
\n<!--\n \n-->\n
\n\n
\n
\nfunction yourmodule_form_alter(&$form, &$form_state, $form_id) {\n if ($form_id == 'user_login') {\n $form['#validate'][] = 'yourmodule_external_validate';\n }\n}\n
\n
\nroles);\n if ($access_granted) {\n return TRUE;\n }\n else {\n form_set_error('', t('Only site administrator can login.'));\n return FALSE;\n }\n }\n}-->
\nroles);\n if ($user_access_granted) {\n form_set_error('', t('Only front user can login.'));\n return FALSE;\n }\n else {\n return TRUE;\n }\n}-->
\nroles);\n if ($access_granted) {\n return TRUE;\n }\n else {\n form_set_error('', t('Only site administrator can login.'));\n return FALSE;\n }\n }\n else {\n $user = user_load($form_state['uid']);\n $user_access_granted = in_array('administrator', $user->roles);\n if ($user_access_granted) {\n form_set_error('', t('Only front user can login.'));\n return FALSE;\n }\n else {\n return TRUE;\n }\n }\n}-->
\nset_error_handler('errorHandler'); // this line of code sets an error handler custom function to handle any php error. And here we pass our custom function that name “errorHandler”\n\nfunction createTable($array){\n if(is_array($array) && count($array)>0){\n $errorContent = "<table border = 1><tr><td>";\n foreach ($array as $key => $val) {\n $errorContent .= $key . "</td><td>";\n if(is_array($val) && count($val)>0){\n $errorContent .= createTable(json_decode(json_encode($val),true)) ;\n }else{\n $errorContent .= print_r($val, true) ;\n }\n }\n $errorContent .= "</td></tr></table>";\n return $errorContent;\n }\n return '';\n}\n \n/**\n * \n * @param type $errorNumber // This parameter returns error number.\n * @param type $errorString // This parameter returns error string.\n * @param type $errorFile // This parameter returns path of file in which error found.\n * @param type $errorLine // This parameter returns line number of file in which you get an error.\n * @param type $errorContext // This parameter return error context.\n */\nfunction errorHandler($errorNumber, $errorString, $errorFile, $errorLine, $errorContext) {\n $emailAddress = 'example@example.com';\n $emailSubject = 'Error on my Application';\n $emailMessage = '<h2>Error Reporting on :- </h2>[' . date("Y-m-d h:i:s", time()) . ']';\n $emailMessage .= "<h2>Error Number :- </h2>".print_r($errorNumber, true).'';\n $emailMessage .= "<h2>Error String :- </h2>".print_r($errorString, true).'';\n $emailMessage .= "<h2>Error File :- </h2>".print_r($errorFile, true).'';\n $emailMessage .= "<h2>Error Line :- </h2>".print_r($errorLine, true).'';\n $emailMessage .= "<h2>Error Context :- </h2>".createTable($errorContext);\n $headers = "MIME-Version: 1.0" . "rn";\n $headers .= "Content-type:text/html;charset=UTF-8" . "rn";\n mail($emailAddress, $emailSubject, $emailMessage, $headers); // you may use SMTP, default php mail service OR other email sending process\n}
\nCommon config files on other platforms are listed below:\n\n
\n","frontmatter":{"date":"October 26, 2015","updated_date":null,"description":null,"title":"How to Get Email Alerts for Unhandled PHP Exceptions","tags":["PHP","Email"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1,"src":"/static/4a396ee0a823348eb1c43701756c8981/7d145/email-alerts-unhandled-php.png","srcSet":"/static/4a396ee0a823348eb1c43701756c8981/69585/email-alerts-unhandled-php.png 200w,\n/static/4a396ee0a823348eb1c43701756c8981/497c6/email-alerts-unhandled-php.png 400w,\n/static/4a396ee0a823348eb1c43701756c8981/7d145/email-alerts-unhandled-php.png 610w","sizes":"(max-width: 610px) 100vw, 610px"}}},"author":{"id":"Team LoginRadius","github":"LoginRadius","avatar":null}}}},{"node":{"excerpt":"So last week while I was setting the analyzers on ElasticSearch settings for Email field, it took me some good time to find the perfect…","fields":{"slug":"/engineering/elastic-search-analyzers-for-emails/"},"html":"\n \n\n\nCMS/application name \nLocation of common file \n\n \n4Images Gallery \n/config.php \n\n \nB2 Evolution \n/conf/_basic_config.php \n\n \nBoonex Dolphin \n/inc/header.inc.php \n\n \nConcrete5 \n/config/site.php \n\n \nCoppermine Photo Gallery \n/include/config.inc.php \n\n \nCrafty Syntax Live Help \n/config.php \n\n \nCube Cart \n/includes/global.inc.php \n\n \ndotProject \n/includes/config.php \n\n \nDrupal \n/sites/default/settings.php \n\n \ne107 \n/e107_config.php \n\n \nFAQMasterFlex \n/faq_config.php \n\n \nGallery \n/config.php \n\n \nGeeklog \n/db-config.php or /siteconfig.php or /lib-common.php \n\n \nglfusion \n/private/db-config.php \n\n \nHotaru \n/hotaru_settings.php \n\n \nJoomla \n/configuration.php \n\n \nLiveSite \n/livesite/config.php \n\n \nLifeType \n/config/config.properties.php \n\n \nMambo \n/configuration.php \n\n \nMarketecture \n/include/config.php \n\n \nMODx \n/manager/includes/config.inc.php \n\n \nMoodle \n/config.php \n\n \nMyBB \n/inc/config.php \n\n \nNoahs Classifieds \n/app/config.php \n\n \nNucleus \n/config.php \n\n \nocPortal \n/info.php \n\n \nOpenCart \n/config.php or /admin/config.php \n\n \nosCommerce \n/includes/configure.php or /admin/includes/configure.php \n\n \nOxwall \n/ow_includes/config.php \n\n \nPHP-Nuke \n/config.php \n\n \nphpBB \n/config.php \n\n \nphpFormGenerator \n/index.php or /mysql.class.php \n\n \nphpFreeChat \n/forms/admin/config.inc.php (only if you have saved form input to a database) \n\n \nPHPlist \n/config/config.php \n\n \nphpMyDirectory \n/defaults.php \n\n \nphpWCMS \n/include/inc_conf/conf.inc.php \n\n \nphpWebSite \n/conf/config.php \n\n \nPhpWiki \n/admin.php or /lib/config.php \n\n \nPligg \n/libs/dbconnect.php \n\n \nPost-Nuke \n/config.php \n\n \nPrestaShop \n/config/settings.inc.php \n\n \nSaurus CMS \n/config.php \n\n \nShopSite \n/includes/configure.php or /admin/includes/configure.php \n\n \nSiteframe \n/config.php \n\n \nSimple Machines Forum \n/Settings.php \n\n \nSoholaunch \n/sohoadmin/config/isp.conf.php \n\n \nSugarCRM \n/config.php \n\n \nTextpattern \n/textpattern/config.php \n\n \nTikiWiki \n/db/local.php \n\n \nTomato Cart \n/includes/configure.php \n\n \nTYPO3 \n/typo3conf/localconf.php \n\n \nWebCalendar \n/includes/settings.php \n\n \nWHMCS \n/configuration.php \n\n \nWordPress \n/wp-config.php \n\n \nX7 Chat \n/config.php \n\n \nXoops \n/mainfile.php \n\n \nZen Cart \n/includes/configure.php or /admin/includes/configure.php \n\n \n\nZikula \n/config.php \n\n
\n\"john.doe@gmail.com\", I also want to be able to search for \"john.doe\" or \"gmail.com\" to retrieve the relative information.\n
\n
\n[Search > Response]
\n\"john.doe@gmail.com\" > 1,2
\n\"john.doe@outlook.com\" > 2,4
\n\"john@yahoo.com\" > 5
\n\"john.doe\" > 1,2,3,4
\n\"john\" > 1,2,3,4,5
\n\"gmail.com\" > 1,2
\n\"outlook.com\" > 2,3,4
\nSo... In the official documentation they did have a good solution but it was not easy to find, at least for me, by using regular expression:
\n{\n "settings" : {\n "analysis" : {\n "filter" : {\n "email" : {\n "type" : "pattern_capture",\n "preserve_original" : 1,\n "patterns" : [\n "([^@]+)",\n "(\\p{L}+)",\n "(\\d+)",\n "@(.+)"\n ]\n }\n },\n "analyzer" : {\n "email" : {\n "tokenizer" : "uax_url_email",\n "filter" : [ "email", "lowercase", "unique" ]\n }\n }\n }\n }\n}
\nAt the end I want to share two good gadgets that I found very helpful with ES analyzers and regular expression.\n
\n","frontmatter":{"date":"October 15, 2015","updated_date":null,"description":null,"title":"ElasticSearch Analyzers for Emails","tags":["Elastic Search","Analyzers"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.9230769230769231,"src":"/static/db4c939fb2ba73abdc984760c0082348/ee604/elastic-search.png","srcSet":"/static/db4c939fb2ba73abdc984760c0082348/69585/elastic-search.png 200w,\n/static/db4c939fb2ba73abdc984760c0082348/497c6/elastic-search.png 400w,\n/static/db4c939fb2ba73abdc984760c0082348/ee604/elastic-search.png 800w,\n/static/db4c939fb2ba73abdc984760c0082348/f3583/elastic-search.png 1200w,\n/static/db4c939fb2ba73abdc984760c0082348/5707d/elastic-search.png 1600w,\n/static/db4c939fb2ba73abdc984760c0082348/a16c9/elastic-search.png 3422w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Lucius Yu","github":null,"avatar":null}}}},{"node":{"excerpt":"Integrating social into your site can drastically improve user engagement with your platform. Below are a few useful solutions and…","fields":{"slug":"/engineering/simple-social-media-solutions/"},"html":"
\nThis Elastic Search tool allows you to quickly apply different analyzers, tokenizers and filters to your input, fork it here:
\nElasticsearch InquisitorSocial Login
\n
\nFacebook: How to Implement Facebook Social Login
\nTwitter: Integrating Twitter Social Login
\nLinkedIn: Integrating LinkedIn Social Login on a WebsiteSocial Sharing
\n\n
\n
\n<!---->\n
\n\n
\n
\na. box_count
\nb. button_count
\nc. button
\nd. icon_link
\ne. icon
\nf. link
\n<!-- -->
\nTwitter Follow Company
\n\n
\n
\n<!---->\n
\n
\n<!-- Follow @TwitterDev -->
\nFacebook Social Linking
\n
\nAll you need to do is create a link tag on your page:
\n<!--Facebook-->
\nYou can store the image locally and include it in the a tag:
\n<!--<img src="" alt="Facebook"> -->Conclusion
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\n\n
\nHow is User Authentication Affected?
\nExternal Identity Providers
\nWeb SSO
\nexample.com, travel.example.com, stay.example.com, and web SSO is handled by auth.example.com. In this case, third-party cookie restrictions don’t apply.Federated SSO
\n\n
\nChrome’s Alternatives for Third-Party Cookies
\n\n
\nCookies Having Independent Partitioned State (CHIPS)
\na.com with a map embed from map-example.com, which can set a partitioned cookie that is only accessible on a.com. b.com with a map embed from map-example.com, it cannot access the partitioned cookie set on a.com. It has to create a separate partitioned cookie specific to b.com, thus blocking cross-site tracking yet allowing limited cross-site functionality.Storage Access API
\nRelated Website Sets
\nprimary website and associatedSites for limited purposes to grant third-party cookie access and local storage for a limited number of sites.resuestStorageAccessFor() API.Federated Credential Management (FedCM) API
\n\n
\nHow is LoginRadius Preparing for the Third-party Cookie Phase-out?
\nIn Conclusion
\nGlossary
\na.com, which might use an embed from loginradius.com to facilitate authentication. If loginradius.com sets a cookie when the user visits a.com, it is called a third-party cookie as the user hasn’t directly visited loginradius.com.References
\n\n","frontmatter":{"date":"July 08, 2024","updated_date":null,"description":"Google Chrome has planned to phase out third-party cookies, which will affect different website functionalities depending on third-party cookies. This blog focuses on how this phase-out affects identity and user authentication and discusses alternatives for overcoming challenges.","title":"How Chrome’s Third-Party Cookie Restrictions Affect User Authentication?","tags":["Identity","Cookies","Chrome"],"pinned":null,"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png","srcSet":"/static/eb7396060c0adc430dbed2d04b63d431/69585/third-party-cookies-phaseout-chrome.png 200w,\n/static/eb7396060c0adc430dbed2d04b63d431/497c6/third-party-cookies-phaseout-chrome.png 400w,\n/static/eb7396060c0adc430dbed2d04b63d431/ee604/third-party-cookies-phaseout-chrome.png 800w,\n/static/eb7396060c0adc430dbed2d04b63d431/f3583/third-party-cookies-phaseout-chrome.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Raghunath Reddy","github":"raghunath-r-a","avatar":null}}}},"pageContext":{"limit":6,"skip":270,"currentPage":46,"type":"//engineering//","numPages":52,"pinned":"17fa0d7b-34c8-51c4-b047-df5e2bbaeedb"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}