# otp Published articles for otp. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What Is SMS Pumping Fraud and How to Stop It DevFeed: [What Is SMS Pumping Fraud and How to Stop It]() Original publisher: [Read original article]() Author: Twilio Published: 2026-09-10T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Security](), [Messaging](), [Bot](), [Authentication](), [Forms](), [Chat Bot]() Tags: [authentication](), [automated](), [bots](), [fraud](), [how-to](), [industry-insights](), [messaging](), [otp](), [security](), [verification]() ### AI overview This article explains SMS pumping fraud, also known as SMS toll fraud, in which attackers use bots and fake phone numbers to trigger large volumes of automated SMS messages. It describes impacts such as increased messaging costs and reduced conversion rates, and introduces detection and prevention measures. ### Source excerpt SMS pumping fraud is an urgent problem for businesses that use SMS. Learn more about SMS pumping and how to prevent it. ## Fill an SMS Verification Code Without Reading the Inbox DevFeed: [Fill an SMS Verification Code Without Reading the Inbox]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-09-07T00:00:00Z Content type: tutorial Language: en Sources: [CodeName One]() Topics: [Android](), [iOS](), [Web](), [Security](), [API](), [Accessibility]() Tags: [accessibility](), [android](), [api](), [asynchronous](), [ios](), [otp](), [permission](), [security]() ### AI overview Codename One adds one-time-code autofill, a country-aware phone-number field, and a verification component for iOS, Android, and the browser without requesting access to the rest of the SMS inbox. The article explains the asynchronous verification flow, server-side security responsibilities, and a single-editor design that improves typing, pasting, accessibility, and autofill. ### Source excerpt Codename One adds phone-number and OTP components plus one-time-code autofill on iOS, Android, and the web without requesting permission to read SMS messages. ## Recovery Authentication Codes DevFeed: [Recovery Authentication Codes]() Original publisher: [Read original article]() Author: Ricardo Martin Camarero Published: 2025-10-20T00:00:00Z Content type: tutorial Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authentication](), [MFA](), [passwords](), [WebAuthn]() Tags: [authentication](), [idm](), [kerberos](), [keycloak](), [ldap](), [openid-connect](), [otp](), [passwords](), [recovery](), [saml](), [sso]() ### AI overview This Keycloak article explains recovery authentication codes, a supported feature since version 26.3.0. It describes them as twelve sequential, one-time passwords that provide a backup second-factor method when an OTP or WebAuthn device is unavailable, and outlines how administrators enable and require them. ### Source excerpt Recovery Codes are a supported authentication method in Keycloak since version 26.3.0. At that time, the new feature was not properly presented in this blog, but this new entry tries to address that oversight. If you prefer watching a video instead of reading this blog, Niko Köbler published Keycloak Recovery Authentication Codes in youtube. Although the video is two years old, when the feature was in preview, it still stands for almost everything and it is very recommendable. This entry updates the recovery codes status when the feature is finally supported. What are Recovery authentication codes? Recovery codes are a Second Factor Authentication (2FA) method which can be used as a backup option to avoid losing access to your account. Therefore, they can be configured or enabled in the authentication flow to give another chance to login in case the OTP or WebAuthn device is unavailable (for example your phone or yubikey are broken or lost). Technically the recovery codes are twelve sequential one-time passwords auto-generated by Keycloak. The authentication process asks the user for the next generated code in order. When that code is introduced, it is removed and the following code will be required in the subsequent login. Enable recovery codes for authentication The default browser flow already contains recovery codes as a 2FA sub-step, but the authenticator is disabled by default. You just need to enable it to make it available for the login. In the administration console, Authentication -> Flows, select the browser flow. Under the step Browser - Conditional 2FA, OTP Form is set to Alternative, but Recovery Authentication Code Form is Disabled. Change the latter to Alternative too. With this configuration, both alternative methods are available to login. Recovery codes can be integrated in more complex authentication flows if needed. Setup recovery codes for the final user The administrator can force any account to setup the recovery codes credentials assigning th ## Keycloak 26.3.0 released DevFeed: [Keycloak 26.3.0 released]() Original publisher: [Read original article]() Author: Keycloak Team Published: 2025-07-03T00:00:00Z Content type: release Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [releases](), [Authentication](), [Logging](), [Passkeys](), [WebAuthn](), [migration](), [OAuth 2.0](), [openid](), [Latency]() Tags: [authentication](), [idm](), [kerberos](), [keycloak](), [keycloak-release](), [latency](), [ldap](), [logging](), [migration](), [new-feature](), [oauth-2-0](), [openid-connect](), [otp](), [release](), [releases](), [saml](), [sso]() ### AI overview Keycloak 26.3.0 is a software release that adds supported 2FA recovery codes, simplifies WebAuthn and Passkeys registration and account linking, expands OAuth 2.0 and OpenID Connect connectivity, improves logging throughput and latency, and introduces experimental rolling updates for patch releases. ### Source excerpt To download the release go to Keycloak downloads. Highlights This release delivers advancements to optimize your system and improve the experience of users, developers and administrators: Account recovery with 2FA recovery codes, protecting users from lockout. Simplified experiences for application developers with streamlined WebAuthn/Passkey registration and simplified account linking to identity providers via application initiated actions. Broader connectivity with the ability to broker with any OAuth 2.0 compliant authorization server, and enhanced trusted email verification for OpenID Connect providers. Asynchronous logging for higher throughput and lower latency, ensuring more efficient deployments. For administrators, experimental rolling updates for patch releases mean minimized downtime and smoother upgrades. Read on to learn more about each new feature, and find additional details in the upgrading guide if you are upgrading from a previous release of Keycloak. Recovering your account if you lose your 2FA credentials When using for example a one-time-password (OTP) generators as a second factor for authenticating users (2FA), a user can get locked out of their account when they, for example, lose their phone that contains the OTP generator. To prepare for such a case, the recovery codes feature allows users to print a set of recovery codes as an additional second factor. If the recovery codes are then allowed as an alternative 2FA in the login flow, they can be used instead of the OTP generated passwords. With this release, the recovery codes feature is promoted from preview to a supported feature. For newly created realms, the browser flow now includes the Recovery Authentication Code Form as Disabled, and it can be switched to Alternative by admins if they want to use this feature. For more information about this 2FA method, see the Recovery Codes chapter in the Server Administration Guide. Performance improvements to import, export and migration The time ## Jetpack Compose OTP input field DevFeed: [Jetpack Compose OTP input field]() Original publisher: [Read original article]() Author: Ban Markovic Published: 2022-12-19T14:51:05Z Content type: tutorial Language: en Sources: [Stories by Ban Markovic on Medium]() Topics: [Jetpack Compose](), [Compose](), [Android](), [android-development](), [Mobile](), [ui](), [Code](), [Development](), [Authentication](), [implementation](), [Material Design](), [passwords]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [authentication](), [code](), [component](), [compose](), [compose-ui](), [development](), [implementation](), [jetpack-compose](), [kotlin](), [material-design](), [mobile](), [mobile-apps](), [otp](), [password](), [ui]() ### AI overview A tutorial on building a customizable one-time password input field for Android with Jetpack Compose and BasicTextField. It explains why BasicTextField can be preferable to Material TextField for customization, configures a numeric password keyboard, and limits input to six digits. ### Source excerpt One-time password (OTP), also called dynamic password, one-time PIN, and one-time authorization code (OTAC), is password that is only valid for one login session. Most commonly, it is received in a format of 4 or 6 digit code, through SMS, and it used for implementation of two-factor authentication. Implementing OTP support inside our mobile apps requires us to build a custom UI input field, which should be strictly customized for handling the received OTP code. Motivation Since Jetpack Compose is a new UI toolkit for Android development, I wanted to write an article regarding how we can make our own custom OTP input field using BasicTextField. Custom OTP input Creating input fields with Compose UI is quite simple. There is already an existing Material component called TextField, that we can use. It has a lot of built-in functionalities because it follows Material design principles. That also comes with some drawbacks, for example, if we wanted to customize our input field, we would have struggled to do so with TextField, because it isn't as flexible. That's why we need another component that is a bit lower-level compared to TextField, but it enables us to customize it the way that suits us the best. I'm talking about BasicTextField. Implementation Firstly, lets implement a simple BasicTextField that enables it to open a keyboard with only numbers. We can do that by setting up the keybaordOptions parameter with keyboardType set to NumberPassword. If you've wondered why we use NumberPassword and not just Number, it is because the keyboard that is opened for the Number keyboard type contains dot, comma and dash characters, and we don't need anything other than digits inside our OTP input field. Next step we need to do is to implement more restrictions inside our input field. In case we know that our OTP must be a 6 digit code, our input field should be able to receive max 6 digits, and not allow user to input more than that. To accomplish max characters restriction, w ## Replenysh uses Supabase to implement OTP in less than 24-hours DevFeed: [Replenysh uses Supabase to implement OTP in less than 24-hours]() Original publisher: [Read original article]() Published: 2021-10-19T07:00:00Z Content type: article Language: en Sources: [Supabase Blog]() Topics: [Supabase](), [Authentication](), [Back end](), [DevOps](), [Code]() Tags: [authentication](), [backend](), [customers](), [devops](), [implement](), [otp](), [passwords](), [postgres](), [products](), [refactoring]() ### AI overview The article presents Replenysh's use of Supabase to implement OTP in less than 24 hours. It highlights a streamlined authentication experience, reduced DevOps overhead, and continued scaling with Postgres while describing Replenysh's circular-economy platform. ### Source excerpt Learn how Replenysh uses Supabase to power the circular economy, redefining how brands interact with their customers and products. ## Erlang rebar tutorial: generating releases and upgrades DevFeed: [Erlang rebar tutorial: generating releases and upgrades]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2011-03-26T05:00:00Z Content type: tutorial Language: en Sources: [Richard Jones]() Topics: [Erlang](), [Tutorial](), [releases](), [Development](), [make]() Tags: [appup](), [code](), [deploy](), [development](), [erlang](), [gnu-linux](), [make](), [otp](), [production](), [programming](), [project](), [rebar](), [releasehandler](), [releases](), [sasl](), [tutorial](), [upgrades]() ### AI overview A tutorial on using rebar to structure, compile, package, deploy, and upgrade Erlang applications. It demonstrates creating releases that bundle the Erlang VM, required OTP libraries, application code, and dependencies, enabling installation of new versions without downtime. ### Source excerpt During my experiments with rebar, I made a simple example app for testing upgrades and releases. This article will walk you through using rebar to create an application, lay it out properly, package and deploy it, and create and install new versions without downtime. ## Erlang/OTP releases: rebar, release\_handler, .appup, etc DevFeed: [Erlang/OTP releases: rebar, release\_handler, .appup, etc]() Original publisher: [Read original article]() Author: {"image"=\>"rj-headshot.jpg", "greetings"=\>nil} Published: 2010-09-18T05:00:00Z Content type: opinion Language: en Sources: [Richard Jones]() Topics: [Erlang](), [releases](), [upgrade](), [modules]() Tags: [appup](), [deployment](), [erlang](), [hacks](), [irc](), [irccloud](), [mochiweb](), [otp](), [programming](), [release](), [releases](), [sasl](), [sysops](), [upgrade]() ### AI overview An Erlang developer describes deploying live upgrades for running OTP applications behind an in-browser IRC client. The article discusses release packaging, release_handler, .appup files, rebar, and an upgrade from R13B to R14 after encountering upgrade-related problems. ### Source excerpt I've been building something in Erlang recently, provisionally called IRCCloud.com (mention this post if you request an invite!) - it's an in-browser IRC client that stays connected for you all the time, so you never miss the conversation. You can reopen your browser later and still have all the backlog. IRC is damn useful, and James and I are building IRCCloud to give you the advantages of IRC bouncer-esque functionality, with the ease of just opening a webpage.