meshStack

meshStack

  • User Docs
  • Administrator Docs
  • API Docs
  • Release Notes
  • Feedback

›Cloud Foundry

Getting Started

  • How to get started with meshStack
  • AWS S3 Quickstart Guide
  • AKS Platform Quickstart Guide
  • AKS Developer Platform Guide

Concepts

  • Overview
  • Administration Roles
  • Onboarding
  • meshWorkspaces
  • meshProjects
  • meshTenants
  • Replication Configuration
  • Delete Tenants
  • meshUsers
  • meshPlatforms
  • Landing Zones
  • Open Service Brokers (OSB)
  • Guide: Emergency Users
  • Managing Tags
  • Policies
  • Unmanaged Tenants
  • meshStack Settings
  • Workspace Services
  • API Users
  • DNS and SSL Certificates
  • Customizing
  • Product Feedback Collection

Identity & Access

  • Identity and Access Management
  • Identity Provider
  • Identity Lookup
  • Authorization
  • User & Group LDAP Synchronisation
  • User & Group SCIM Synchronisation

Building Blocks

  • Building Blocks
  • Private Runners
  • Terraform/OpenTofu state managed by meshStack
  • Permission Delegation on AWS
  • Connecting meshStack and a Pipeline

Metering & Billing

  • Cost Management
  • Configuration

Amazon Web Services

  • Integration
  • Landing Zones
  • Metering
  • SSO Setup
  • Reserved Instances & Savings Plans Guide

Microsoft Azure

  • Integration
  • Landing Zones
  • Metering

Google Cloud Platform

  • Integration
  • Landing Zones
  • Metering

Cloud Foundry

  • Integration
  • Metering

Kubernetes

  • Integration
  • Landing Zones
  • Metering

GitHub

  • Pipeline Automation
  • Repository Provisioning

OpenShift

  • Integration
  • Landing Zones
  • Metering

OpenStack

  • Integration
  • Metering

OSB Services

  • Integration
  • Metering
  • meshcloud OSB API Profile
  • Tenant Services
  • Tutorial: Implement a Broker

Operations

  • Managed Service
  • Email
  • Logging & Auditing
  • Monitoring & Telemetry
  • Backup
  • Security FAQ

Guides

  • How to integrate a meshPlatform into meshStack
  • How to manually integrate AWS as meshPlatform
  • How to manually integrate Azure as meshPlatform
  • How to manually integrate GCP as meshPlatform
  • How to create your own platform
  • How to manage partner level permissions
  • How to use scoped API keys
  • How to setup and manage a Building block
Edit

Integration

meshStack supports integration with Cloud Foundry. Cloud Foundry is a PaaS platform which provides convenient application hosting capabilities to software and DevOps engineers.

meshStack supports project creation, configuration, access control, quota management and billing for Cloud Foundry.

Integration Overview

To enable integration with Cloud Foundry, Platform Operators configure one or multiple Platforms of PlatformType Cloud Foundry in the Platform Administration in meshPanel.

Prerequisites

Your Cloud Foundry must support the v3 Cloud Foundry API. We have officially validated meshStack with support for Cloud Foundry v3.108.0.

UAA Federated Users

meshStack will identify and assign users to roles in Cloud Foundry based on their euid (external user id) as described in Identity Federation.

You should set up your Cloud Foundry and UAA so that they store the euid value in the User.userName field of the UAA User object and User.username field of the Cloud Foundry user object.

Integration Configuration

The recommended way to set up Cloud Foundry as a meshPlatform is via the public terraform Cloud Foundry meshPlatform Module.

meshStack Admin User Accounts

meshStack requires two technical admin user accounts for integration with Cloud Foundry. We recommend your assign these users the following Cloud Foundry roles and UAA scopes.

  • the replicator admin account must have permission to create orgs, spaces, groups and assign roles. This user requires the Admin role and additionally needs the cloud_controller.admin, uaa.admin and scim.read scopes in UAA.
  • the metering admin account is used to collect metering data. This requires the Global Auditor.

The tenant replication ensures spaces and orgs are created within the CF platform and appropriate permission rights are set when users access the CF platform. If a user's project permissions are modified, meshStack updates the permissions for this user accordingly within the CF platform.

Spaces & Organizations

By default, meshStack will replicate tenants as Cloud Foundry Spaces and create a Cloud Foundry Organization for every workspace.

Permission Replication

During replication, meshStack will make sure that users have access to the Cloud Foundry spaces they are assigned to in meshStack. It is currently not possible to configure a custom role mapping for Cloud Foundry landing zones. All meshStack project roles will be mapped to the Space Developer role in Cloud Foundry.

Users will additionally receive the Org User role on the Organization created for their workspace.

Last updated on 5/8/2024
← MeteringMetering →
  • Integration Overview
  • Prerequisites
    • UAA Federated Users
  • Integration Configuration
    • meshStack Admin User Accounts
    • Spaces & Organizations
    • Permission Replication
meshStack
Docs
User DocumentationAdministrator DocumentationSecurity FAQ
Get in Touch
SupportWebsiteLinkedIn
More
Release NotesGitHub
Copyright © 2025 meshcloud GmbH