Using Custom Fonts In Service Portal - PUBLIC Pages

[Andrew Pishchul]

I'm trying to use custom fonts (font icons) in Service Portal on a public page, but with no success. There is a great post with multiple options on how to add custom fonts (Using Custom Fonts In Service Portal) and Options #3 works perfect for logged in users. However, it doesn't work for a public role.

I tried read ACLs for sys_attachment and sp_css tables with public role, but with no success.

Any ideas on how to make custom fonts available for a public page?

[Brad Tilton]

Base64 encoding the font files and putting them in the css include should work (option 2).

[nathanfirth]

If base64 encoding doesn't work (doesn't always work with all fonts), I would recommend hosting the font files on a CDN or Amazon S3.

[mandle]

I feel your pain Andrew.

This is especially crucial for B2C interactions. Where many customers (using that word here to mean external to the business) are accessing all kinds of "attachments". At some point (now) the Attachment APIs will need to accomodate "unauthenticated access". And yes I fully acknowledge how non-trivial an effort this iwill be and bravo to those that may be working on it right now!

For Fonts and other "certified" web assets it would be sweet to have a ServiceNow CDN, for ServiceNow customers only.
I know that some ServiceNow clients shy away from dependance upon yet another cloud resource.

[Andrew Pishchul]

In fact, Option #2 works absolutely fine for me.. with one exception - free tool by Font Squirrel doesn't work with all font types, so I just used base64 macOS/linux command to encode the icon font.