
OAuth Experts in Stuttgart
matched in minutes from over 15,000 CVsHire experts who design secure authorization flows, connect identity providers, and integrate OAuth with APIs, OpenID Connect, and cloud applications. FRATCH matches you quickly and precisely with vetted, available freelancers for your project.
Meet FRATCH Experts in Stuttgart, who have recently used OAuth
Robert B.
Last position:
Digital fault reporting portal, custom ticketing system at Municipal client
Digital fault reporting portal, custom ticketing system
Project type: Web development / custom development / operational application software
Technology: Neos CMS, Flow Framework, MySQL, Dexie.js, PhpSpreadsheet
Status: Delivered
Background:
Faults in the client’s day-to-day operations and facilities had previously been reported by phone, on paper or by email and coordinated manually. There was no structured follow-up, clear assignment of responsibilities or complete documentation. A particularly critical issue was that field staff on site had no direct access to a central system – fault reports were created in isolation and information was lost.
Market research also showed that common helpdesk or ticketing systems did not adequately cover the specific requirements of municipal wastewater management – decentralized facilities, on-call duty coordination and integration with existing communication channels. Custom development was the only sensible solution.
Solution:
The client received a custom web-based fault reporting portal, developed from the ground up for the company’s exact operational processes. The system combines structured ticket creation, traceable status tracking, mobile field reporting and automated notifications in a single, low-maintenance platform.
Ticket lifecycle and audit trail:
Every fault report follows a clearly defined lifecycle:
- New
- In progress
- Under observation
- Completed
- Rejected
Every status change is logged immutably: who changed what, when – and why. The StateChange model ensures that the complete processing history can be traced at any time. In addition, staff can comment directly on tickets, ask questions and post status updates – keeping everyone on the same page without email chains.
Roles and permissions:
The portal has three user roles with fine-grained access rights:
- Admin – full system access, user management, department configuration
- Manager – processing and management of all reports within their area of responsibility
- Employee – creating and viewing their own and assigned reports
Department assignments automatically determine which tickets a user sees and which notifications are triggered.
Mobile tablet support with offline synchronization:
Employees report faults directly on site – at a manhole, in a machine room or outdoors. A dedicated tablet mode was developed for this purpose:
- Tablets are registered once and activated using a token-based process
- When there is no network connection, the system stores reports locally in the browser (IndexedDB via Dexie.js)
- As soon as a network connection is available, all reports created offline are synchronized automatically – no data loss and no manual reconciliation
- Photos can be uploaded directly from the tablet camera and linked to the ticket
This mechanism solves a key practical problem at wastewater treatment plants: reporting under difficult conditions, far from the office Wi-Fi.
Department-based notification system:
Each fault report is assigned to one or more of the twelve specialist departments.
As soon as a report is created, edited or moved to a new status, the responsible department contacts automatically receive an email. Notification settings can be configured individually for each user – no noise and no missed reports.
On-call duty management:
The portal integrates on-call duty management directly into the fault reporting process. On-call groups (RB1, RB2, RB3) are stored and managed in the system. Incoming faults can be assigned directly to the staff on duty – the on-call schedule and ticketing system are no longer separate worlds.
Cost tracking and Excel reporting:
Cost center codes and expenses can be recorded for each fault report – useful for internal cost allocation and budget control. The system allows all reports and cost data to be exported as an Excel file for monthly reports, analysis and transfer to other systems.
Technical implementation:
The portal was delivered as a custom solution based on Neos CMS / Flow Framework (PHP) – an enterprise framework with a clear MVC architecture, Doctrine ORM database abstraction and integrated access control. The MySQL database documents the continuous development of the data model since the project began in 2016 through more than 20 migration versions.
Dexie.js (an IndexedDB wrapper) provides offline functionality, using proven browser technology for robust client-side data persistence. The sync mechanism is implemented through a dedicated API endpoint and was carefully designed to be idempotent and conflict-free.
The core data model includes 13 entities (Report, Department, Location, Tablet, Cost, Image, Ondutygroup, Post, StateChange, among others), 11 controllers and over 25 configured API routes – complexity that a standard product could not provide without significant customization.
Benefits for the client:
- Fault reporting: phone, paper, email → structured web portal, including offline use
- Traceability: none → complete audit trail of all status changes
- Responsibilities: verbal and unclear → department assignment and role-based permissions
- Notifications: manual → automatic, configurable by department
- Field reporting: not possible → tablet app with offline sync and photo uploads
- On-call duty: managed separately → integrated into the fault reporting portal
- Reporting: compiled manually → Excel export at the click of a button
- Document history: none → complete, with timestamp and user
Result:
The company now has an operationally proven, fully custom ticketing system that accurately reflects the real processes of municipal wastewater management. Twelve specialist departments, three user roles, mobile field staff with offline capability, automated notifications and complete logging form a coherent system – with no breaks between media and no isolated solutions.
The decision to build a custom solution has paid off: a standard product would not have achieved this level of operational integration without significant customization – and would have become more expensive and less flexible in the long run.
Sercan T.
Last position:
Co-Founder & Lead Software Architect at Pflege-Pfad
- Focus: System architecture, cloud-native platforms, microservices, API design
- Product: Pflege-Pfad is a digital placement platform that directly connects relatives of people in need of care with verified care services and caregivers – without an agency and without ongoing fees.
- Business analysis & process design:
- Analysis of the German care market and identification of the key pain points of both target groups.
- Modeling of core business processes: registration, verification, care request, application, placement, and rating.
- Definition of the business model as a freemium/premium model with optional contact unlocking.
- Creation of user stories and requirements documentation for relatives, care services, and administrators.
- Design of trust and quality assurance mechanisms with document upload, admin review process, and rating system.
- Coordination with stakeholders and validation of product decisions with potential users.
- Technical implementation:
- Design and implementation of the entire platform architecture as the sole developer.
- Design and implementation of a REST API with Spring Boot and Kotlin, including JWT-based authentication.
- Development of the frontend as a single-page application with Angular 17.
- Implementation of the AWS infrastructure with EC2, RDS PostgreSQL, S3, CloudFront, and IAM.
- Document upload with AWS S3 using presigned URLs to verify care services.
- Email notifications via Resend API.
- AI-supported care service search via OpenAI API.
- Implementation of complete user flows such as registration, login, password reset, and the placement process.
- Development of an admin panel for user and care service management as well as analytics.
- CI/CD with GitHub Actions and containerized deployments with Docker.
- End-to-end tests with Playwright.
Technologies: Kotlin, Spring Boot 3, Spring Security, JWT, JPA/Hibernate, PostgreSQL, Angular 17, TypeScript, RxJS, AWS (EC2, ECS, S3, CloudFront CDN, RDS PostgreSQL, IAM), nginx, GitHub Actions, Playwright, Maven, Git, OpenAI API, Resend API, Docker, Scrum, i18n (DE/EN/TR), Kiro, feature flag architecture.
Will O.
Last position:
Solution Architect at Polizei Behörde Stuttgart
Designed a migration strategy for WLS applications to BKA Cloud and Stack IT
Created a hybrid cloud for internal testing and development with Kubernetes
Transformed the IT landscape from an outdated monolithic architecture to a cloud-based architecture
Integrated new CI/CD processes using Azure Pipelines
Quadrupled the processing throughput for personnel security checks
Migrated personnel security screening applications to Docker-based applications
Implemented CI/deployment pipelines using Azure DevOps
Environment: Java Springboot, Kubernetes, Oracle Weblogic, OpenID, Camunda, JUnit, TOGAF
Benjamin S.
Last position:
Design and implementation of a new cloud service at Porsche AG
- Design of a new cloud service
- Requirements Engineering
- API Design (REST API, Kafka)
- Consulting on architecture, feasibility and effort estimation
- Implementation of a microservice architecture
- Implementation of a Spring Boot web service
- Development of REST APIs including business and persistence logic
- Kafka consumers and producers
- Various Excel upload/download scenarios
- Change Data Capture
- Cloud provisioning with IaC/Terraform
- Go-live with 30,000 users
- Operation, support and bug fixing for other services
Environment/tools: GitLab, JIRA, Confluence, IntelliJ, Spring Boot, Java, Docker, Terraform, AWS ECS, Postgres, Apache Kafka, SAP Datasphere, JUnit, Debezium, Apache POI, Hibernate, JPA, Testcontainers
Marcel S.
Last position:
Technical Lead / Lead Developer at REWE digital
- Following an organizational restructuring into product-based teams, the decision was made to build a Data Mesh for Digital Supplier Management (DSM).
- Highly available, real-time Data Mesh for providing large volumes of data to other products via Kafka and REST.
- Development of new core supplier management software using a (micro-)service-based architecture and a modern technology stack.
- Technologies/Tools:
- Java 21
- Spring Boot
- Angular
- TypeScript
- Golang
- MapR
- Kafka
- Docker
- Google Cloud Platform (GCP)
- Kubernetes
- Helm
- GitLab CI
- Maven
- JUnit
- Mockito
- WireMock
- Cypress
- Keycloak
- OAuth 2.0 & OpenID Connect
- Humio
- Nexus
- Artifactory
- SonarQube
- Renovate
- Git
- Postman
- IntelliJ
Achille C.
Last position:
Backend/Frontend Developer at ITZ-Bund
- Development of a microservice application for calculating account bookings
- Development of backend components with Java / JEE, Quarkus, Kafka, REST API
- Development of the test component with mocking frameworks (Mockito)
- Development of unit tests with JUnit / ArchUnit, integration test components
- Creation of OpenAPI specification format
- Configuration of CI/CD pipeline
- Development of frontend component with React
- Design, further development and optimization of system architectures
- Migration from MySQL to PostgreSQL
- Code reviews
- Java Corretto 21, JEE, Quarkus, Golang
- Reactive programming with Spring WebFlux, Project Reactor, Liquibase, Elasticsearch, Hibernate, HQL, JPA, SQL
- Git, Azure DevOps for CI/CD pipeline, YAML, JSON, Swagger UI, Postman, REST OpenAPI, Kafka Streams, Kafka Connect, Log4J, JUnit / ArchUnit
- Microservices, Jira, Confluence, MySQL, PostgreSQL, Docker, Kubernetes (deployment via Helm charts)
- Spring Security, OAuth 2, JWT, SonarQube
- IntelliJ, Maven, logging framework Splunk, Agile Scrum method, Nexus, Vaadin V24, build tool Vite
- React, React.JS, Node.js, JavaScript, Tailwind CSS, Agile Scrum method, BITV accessibility, Playwright
Lothar H.
Last position:
Multi-Cloud + Hybrid Cloud Transformations of Enterprise Solutions at IBM and various international clients
Multi-Cloud + Hybrid Cloud Transformations of Enterprise Solutions
- AI-assisted Kubernetes routing and resilience PoCs and testing of solutions for network stabilization and creating redundancy, DREAD and STRIDE Security Assessments, Hybrid Cloud Hosting Refinements, system hardening for clients, backend & datacenter.
- Refinement of routing systems within Kubernetes solutions using Tigera Calico and its network management policies and behavioral profile logs, as well as customized visualization tools to refine resilience and redundancy in fallback automation.
- Clients in the energy utility, network operator, banking, insurance and automotive sectors
Discover over 15,000 top freelancers
Statistics of experts using OAuth
Aggregated from the professional profiles of matched freelancers.
Experience
18 years (Germany: 19 years)

Position duration
4.6 years (Germany: 2.7 years)

Positions per freelancer
17 (Germany: 14)

Top business areas
Information Technology, Product Development, Operations

Top industries
Automotive, Government and Administration, Banking and Finance

Certification focus areas
Information Technology, Operations
Bachelor's degree or higher
100% (Germany: 88%)
Master's degree or higher
43% (Germany: 52%)

Certifications per freelancer
1 (Germany: 2)

Most common languages
German, English, Spanish

Speak two or more languages
86% (Germany: 96%)
Based on our profile pool as of 18 Nov 2026.
Daily rate distribution
The chart shows how the daily rates of experts in this technology in Stuttgart are distributed, based on recent contracts on our platform. Each bar covers a rate range — its height shows the share of experts charging within that range.
Average rates of experts in Stuttgart using OAuth
Rates are based on recent contracts and do not include FRATCH margin.
The average daily rate is the mean of all daily rates from recent contracts of comparable freelancers on our platform.
The median daily rate is the middle value of all daily rates — half of comparable freelancers charge less, half charge more. Unlike the average, it is barely affected by outliers.
Calculated based on our freelancers’ daily rates as of 18 Nov 2026. Actual rates may vary depending on seniority level, experience, skill specialization, project complexity, and engagement length.
OAuth experts industry focus
See which industries our matched freelancers work in most often — every figure is calculated live from the freelancers on FRATCH.
- Automotive (86%)
- Government and Administration (86%)
- Banking and Finance (71%)
- Information Technology (71%)
- Insurance (57%)
- Transportation (57%)
- Manufacturing (57%)
- Healthcare (43%)
Please note that freelancers can work across multiple industries, so percentages overlap.
About the technology
What OAuth does
OAuth is an authorization framework that lets an application access protected resources without handling the user’s password. It is used for delegated access, single sign-on integrations, API authorization, and connections between services. The current standard is OAuth 2.0, with OAuth 2.1 consolidating recommended security practices.
Core flows
OAuth uses roles such as the resource owner, client, authorization server, and resource server. Experts select a suitable flow, usually Authorization Code with PKCE for user-facing applications or Client Credentials for service-to-service access. They define scopes, redirect URIs, consent screens, token lifetimes, and refresh behavior with care.
Ecosystem and tools
OAuth commonly works alongside OpenID Connect, which adds identity information and authentication to the authorization layer. Projects may integrate Keycloak, Auth0, Microsoft Entra ID, Okta, Amazon Cognito, Google Identity, or a custom authorization server. Strong specialists also work with JWT validation, JWKS, TLS, API gateways, and secrets management.
Typical deliveries
- Authorization Code and PKCE flows for web and mobile applications
- Client Credentials integrations for internal and external APIs
- Federation with enterprise identity providers and OpenID Connect
- Scope models, consent journeys, token policies, and revocation
- Migration from implicit or password-based flows to safer patterns
These deliverables support customer portals, partner APIs, SaaS products, mobile applications, and distributed services. In Stuttgart, OAuth expertise is relevant to connected manufacturing, mobility, software, and enterprise systems that exchange data across organizational boundaries.
When to bring in experts
Companies often need freelance expertise when an integration must meet strict security requirements, when several identity providers must work together, or when an existing token design has become difficult to maintain. Warning signs include overly broad scopes, long-lived access tokens, inconsistent claims, redirect errors, weak client storage, and unclear ownership of authorization decisions. Remote collaboration works well when access, test environments, and security contacts are organized; on-site workshops can help with complex enterprise integrations in Stuttgart.
What quality looks like
A strong OAuth professional starts with threat modeling and clear access requirements rather than copying a flow from a library. They distinguish authentication from authorization, validate issuer and audience claims, protect redirect endpoints, handle token rotation, and document scopes and failure paths. They test consent, expiry, replay, revocation, and provider-specific behavior, then leave maintainable integration code, configuration, and runbooks for the internal team.
Frequently asked questions
Questions about OAuth? Start with the answers below.
OAuth lets an application obtain limited access to a user’s or service’s protected resources without receiving the account password. Companies use it for API access, delegated permissions, sign-in integrations, and communication between trusted services.
OAuth is primarily an authorization framework: it describes what an application may access. OpenID Connect builds on OAuth 2.0 to provide an identity layer, including an ID token and standardized user information.
A strong OAuth specialist should understand OpenID Connect, JWT and JWKS validation, API security, TLS, secure secret storage, and identity-provider configuration. Experience with Keycloak, Auth0, Microsoft Entra ID, or another relevant provider is useful when the project depends on a specific ecosystem.
A small, well-documented provider integration may need focused OAuth experience for design review and implementation. A project involving several tenants, identity providers, APIs, or legacy flows benefits from a professional who can model threats, define permissions, and test the complete authorization lifecycle.
OAuth work is usually suitable for remote collaboration because configuration, code review, and testing can happen through secured environments. On-site sessions in Stuttgart can be valuable for workshops with security, product, and infrastructure teams, especially when enterprise access rules are complex.
Ask the OAuth specialist to explain the chosen flow, threat model, scopes, token lifetime, redirect protection, and revocation strategy in plain language. Review whether the implementation separates authentication from authorization and includes tests for expiry, invalid claims, replay, and provider failure.
OAuth is usually stronger than API keys when access must be delegated, scoped, rotated, or tied to a user or service identity. API keys can suit simple server-to-server cases, but they provide less structure for consent, limited permissions, and token lifecycle management.
Before starting OAuth work, clarify the actors, protected resources, identity providers, client types, required scopes, and compliance constraints. Professionals should also confirm who owns secrets, redirect domains, token policies, test accounts, and production incident response.
The average hourly rate of freelancers in Stuttgart, Germany who have used OAuth in their recent projects is 102 €, which corresponds to a daily rate of about 814 € based on an 8-hour working day.
Of the freelancers in Stuttgart, Germany who have used OAuth in their recent projects, 100% hold at least a Bachelor's degree and 43% hold at least a Master's degree.
On average, freelancers in Stuttgart, Germany who have used OAuth in their recent projects have 18 years of professional experience, with a single engagement typically lasting around 4.6 years.
The most common languages among freelancers in Stuttgart, Germany who have used OAuth in their recent projects are German (100%), English (86%), and Spanish (43%).
The most common industries among freelancers in Stuttgart, Germany who have used OAuth in their recent projects are Automotive (86%), Government and Administration (86%), and Banking and Finance (71%).
The most common business areas among freelancers in Stuttgart, Germany who have used OAuth in their recent projects are Information Technology (100%), Product Development (86%), and Operations (71%).
Main locations of FRATCH Experts, who have recently used OAuth
Our freelancers and interim experts are at home across the DACH region — available on-site in the major business hubs or fully remote. Choose a location to discover matched specialists, local market insights and up-to-date availability.
Countries:
Request a free demo
Get in touch with the FRATCH team and we will get back to you within 4 hours.
Would you rather directly get in touch?
We always have the time for a call or email!

Berlin
Hamburg
Munich
Cologne
Frankfurt
Dusseldorf
Dortmund