<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mission Authority Server on Control Plane by Karl McGuinness</title><link>https://notes.karlmcguinness.com/tags/mission-authority-server/</link><description>Recent content in Mission Authority Server on Control Plane by Karl McGuinness</description><generator>Hugo</generator><language>en-us</language><managingEditor>public@karlmcguinness.com (Karl McGuinness)</managingEditor><webMaster>public@karlmcguinness.com (Karl McGuinness)</webMaster><lastBuildDate>Sat, 06 Jun 2026 14:00:00 -0700</lastBuildDate><atom:link href="https://notes.karlmcguinness.com/tags/mission-authority-server/index.xml" rel="self" type="application/rss+xml"/><item><title>Mission Authority Server Profile</title><link>https://notes.karlmcguinness.com/notes/mission-authority-server-profile/</link><pubDate>Sat, 06 Jun 2026 14:00:00 -0700</pubDate><author>public@karlmcguinness.com (Karl McGuinness)</author><guid>https://notes.karlmcguinness.com/notes/mission-authority-server-profile/</guid><description>The default OAuth topology places the Mission record at the Authorization Server. This profile defines a dedicated Mission Authority Server as the state authority. OAuth ASes and AAuth Person Servers become authorized projection issuers. The MAS binds the subject, consent disclosure, canonical Authority Set, lifecycle, and pairwise Mission identifiers. Credential issuers remain responsible for credential validity; the MAS supplies Mission Status.</description></item></channel></rss>