Portal Accounts allows a user to authenticate themself to a portal, so that the portal can keep track of the data belonging to the user and keep it pinned to Skynet. Any Skynet portal can setup their own account parameters, but see the Skynet Guide's Portal Accounts page for more info on how Siasky.net handles user account.
Portal accounts are completely distinct from MySky accounts. MySky accounts are decentralized, work across Skynet, accessed from any portal. A portal account is centralized and works with a single web portal.
For the most part, portal accounts work in the background, out of sight of the user or developer. Requests to the web portal will contain a cookie that is transporting an encrypted JSON Web Token (JWT) which authenticates requests.
For web applications, a user accesses the app through the portal they have an account with. Afterward, uploads and downloads automatically register as to the user for longer pinning and counting towards their storage quotas.
For server-side applications, the application itself will want a user account with a portal. Requests will need to contain the JWT to inform the portal to pin uploaded data.
For more information on using a portal account with server-side, see Server-Hosted Skynet Usage's Using Your JWT.
Web portals can set limits for different user tiers. The limits for Siasky.net are published in our Tier Comparison, and available with more details defined in the code. Bandwidth is listed in bits/second, sizes are in bytes.
To find the limits of the account you're logged in with and confirm you are logged in to a portal account, visit https://account.skynetfree.net/api/user/limits
The limits endpoint on the
accountsubdomain uses a different cookie than the main portal account, so requests to the endpoint will not use the JWT described above.
Skynet Accounts is an open-source service component in the web portal stack -- to learn more about how it is integrated, see the SkynetLabs/skynet-accounts repo.