Using Custom Fonts In Service Portal - PUBLIC Pages

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2017 09:18 AM
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2021 12:25 AM
Hello,
Thank you for your detailed answer.
Unfortunately, Fontsquirel doesn't accept all fonts (I was in this case). Finally, I managed it with another site (https://transfonter.org/) and it worked. The generated code was 7 times lighter than the one I had when running the base64 myself by javascript.
Maybe in the future, ServiceNow will treat fonts like they treat images, so we won't have to use workarounds.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-04-2022 01:47 AM
Worked like a charm, thank you. Especially your screenshots were very helpful!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2023 06:34 AM
Hello,
We have been successfully using the option 2 (base64) until today. In our custom URL, the fonts are suddenly being refused to load because it violates the following Content Security Policy directive: "font-src 'self' https:". Does anybody have a workaround to this one? Or could anybody point me to where I can configure the Content Security Policy directive? Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2024 03:15 AM
Re-linking Nathan's article as the original link is no longer functioning correctly.