Automation recon: portal endpoints and ACP control servers #3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "automation-recon"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Feature
State-only update recording a verified, read-only recon of the iTelescope portal: login flow, DataService.svc JSON endpoints, per-scope ACP control servers (confirmed on T33), planner redirect, weather URLs, and current network status (many scopes offline, incl. recommended T71/T73).
Tools used
curl with a session cookie jar against go.itelescope.net; HTTP-auth probe of the T33 ACP server. No bookings made, no points spent, credentials kept outside the repo.
What was achieved
Session control is confirmed feasible end to end; next steps captured in TODO (map ACP endpoints, explore lookup.itelescope.online, enumerate DataService).