<feed xmlns='http://www.w3.org/2005/Atom'>
<title>progmaweb/apps/web/components/credentials, branch site/phone-layout</title>
<subtitle>The site and account service of Progmasoft: a Next.js frontend and an ASP.NET Core API.</subtitle>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/'/>
<entry>
<title>Fit every page to phones and test the layout with Playwright</title>
<updated>2026-11-16T17:28:33+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-16T17:28:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=537b1f3a4a605b7aa980eec520628ff37648f683'/>
<id>537b1f3a4a605b7aa980eec520628ff37648f683</id>
<content type='text'>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
On a phone the header hid every link but the account button, so the
organization site had no way to its products or developer pages, and the
ViGet, Account and Console headers wrapped onto two or three lines.

- HeaderMenu: below 980px the header holds the brand and a menu button;
  the button opens the links and the preferences as a panel under the
  header (48px rows, 44px controls). Escape, a chosen link or a second
  press closes it. Below 420px the button keeps only its icon, so a brand
  with a product name ("Console", "Account") is never covered. All three
  headers (site, ViGet, credentials) use it; ViGet's own column layout is
  gone. Labels in every locale.
- Header links on wide screens get 10px of vertical padding: the same look,
  40px targets.
- The consent checkbox is 24px.
- product.progmasoft.com: below 560px each project row is a card with
  labelled facts instead of a table that scrolled sideways.
- progmasoft.com: the area tiles beside the hero repeated the list right
  below it; they are hidden once the hero is one column. The OAuth sample
  wraps on phones instead of being cut off.

@playwright/test 1.65.0 runs the built site (next start) in Chromium at
360, 390, 768 and 1280px. Every public host name resolves to the local
server through --host-resolver-rules, so no request leaves the machine.
For one page of each kind on every host it checks: no horizontal scroll,
nothing past the screen edge outside a scrolling box, controls of at least
24 by 24px (WCAG 2.2, 2.5.8), the header on one line with brand and
controls not covering each other; and that the phone menu opens and closes.
The Frontend workflow installs Chromium and runs it after the build,
keeping the report and traces when it fails. 140 tests pass locally; with
the 420px rule removed the overlap check fails on Account and Console.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Name the copyright license alone in SPDX expressions</title>
<updated>2026-11-15T10:14:38+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-11-15T10:14:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=3bda6d7bc28c5aa588418d12d9e3129f8526df50'/>
<id>3bda6d7bc28c5aa588418d12d9e3129f8526df50</id>
<content type='text'>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The Progmasoft Patent Grant is a separate permission added to the
copyright license, not an exception to it, so joining the two with WITH
said something the grant does not do. What makes the grant apply is the
PATENTS notice of the repository (Section 9 of the grant), not the SPDX
expression of each file.

Every project-owned file now carries SPDX-License-Identifier:
AGPL-3.0-or-later, and package.json says the same. PATENTS becomes
PATENTS.md: project-owned software in the repository is covered by the
Patent Grant, Version 1.1, whose canonical text is unchanged under
LICENSES/; third-party material keeps its own terms. NOTICE.txt and the
README point to PATENTS.md.

Claude-Session: https://claude.ai/code/session_01Ji7xZMYjc4zankoc7hGBE1
</pre>
</div>
</content>
</entry>
<entry>
<title>Move the OAuth pages to Next.js and split the authorize host and the console</title>
<updated>2026-10-23T08:02:39+00:00</updated>
<author>
<name>Leitwolf11</name>
</author>
<published>2026-10-23T08:02:39+00:00</published>
<link rel='alternate' type='text/html' href='https://git.progmasoft.com/progmaweb/commit/?id=9099e9fbb50d27b622362b0c2f0dda5085d1fa03'/>
<id>9099e9fbb50d27b622362b0c2f0dda5085d1fa03</id>
<content type='text'>
Progmasoft OAuth now runs on three hosts:

- credentials.progmasoft.com stays the issuer: discovery documents, key
  set, token, user information, revocation and introspection.
- authorize.progmasoft.com serves the pages people see: the
  authorization and end session endpoints (registered with OpenIddict as
  absolute URIs on that host), sign-in, the consent screen and the
  applications an account has allowed.
- console.progmasoft.com is the Progmasoft Console. Its overview links
  the areas; OAuth 2.1 tokens live under /credentials, with New token,
  then the application type, then its form.

The console has no sign-in of its own and never redirects. It uses the
Progmasoft account session, so production now shares that cookie with
progmasoft.com (__Secure-ProgmasoftSession, Domain=progmasoft.com,
HttpOnly, Secure, SameSite=Lax). Without AccountSessions:CookieDomain the
cookie stays host-only with the __Host- name, as in development and tests.

Application types replace the confidential/public switch: web,
single-page, desktop, mobile and service. Each type has its redirection
rules (RFC 8252), its secret or none, and its grants; only a service
uses client credentials and it registers no address or scope. The type is
kept as an application property and cannot change.

The HTML pages of the API are gone. The pages are Next.js pages in four
languages (en-US, de-DE, ru-RU, he-IL) that call JSON endpoints under
/api/v1/oauth. Requests that change state must come from the page's own
origin; antiforgery forms are no longer needed. The token, revocation and
user information endpoints answer CORS requests from the origins of
single-page applications, without credentials; the discovery documents
and the key set answer every origin.

The host filter keeps every path on its host. Nginx gains the authorize
and console virtual hosts, and the docs describe the hosts, the types and
the shared session.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Progmasoft OAuth now runs on three hosts:

- credentials.progmasoft.com stays the issuer: discovery documents, key
  set, token, user information, revocation and introspection.
- authorize.progmasoft.com serves the pages people see: the
  authorization and end session endpoints (registered with OpenIddict as
  absolute URIs on that host), sign-in, the consent screen and the
  applications an account has allowed.
- console.progmasoft.com is the Progmasoft Console. Its overview links
  the areas; OAuth 2.1 tokens live under /credentials, with New token,
  then the application type, then its form.

The console has no sign-in of its own and never redirects. It uses the
Progmasoft account session, so production now shares that cookie with
progmasoft.com (__Secure-ProgmasoftSession, Domain=progmasoft.com,
HttpOnly, Secure, SameSite=Lax). Without AccountSessions:CookieDomain the
cookie stays host-only with the __Host- name, as in development and tests.

Application types replace the confidential/public switch: web,
single-page, desktop, mobile and service. Each type has its redirection
rules (RFC 8252), its secret or none, and its grants; only a service
uses client credentials and it registers no address or scope. The type is
kept as an application property and cannot change.

The HTML pages of the API are gone. The pages are Next.js pages in four
languages (en-US, de-DE, ru-RU, he-IL) that call JSON endpoints under
/api/v1/oauth. Requests that change state must come from the page's own
origin; antiforgery forms are no longer needed. The token, revocation and
user information endpoints answer CORS requests from the origins of
single-page applications, without credentials; the discovery documents
and the key set answer every origin.

The host filter keeps every path on its host. Nginx gains the authorize
and console virtual hosts, and the docs describe the hosts, the types and
the shared session.
</pre>
</div>
</content>
</entry>
</feed>
