nameID edgecase
See original GitHub issuehttps://github.com/alexeiva/Arsenal/issues/4
Arsenal is generating this error, although the naming is proper. @m4rc1e rechecked on his machine and confirmed the issue.
Font lacks entry with nameId=17 (TYPOGRAPHIC_SUBFAMILY_NAME)
ERROR [FONT_FAMILY_NAME(1):WINDOWS(3)] entry: expected 'Arsenal' but got 'Arsenal Bold'
TTFs here
Issue Analytics
- State:
- Created 7 years ago
- Comments:35 (24 by maintainers)
Top Results From Across the Web
Metadata overrides/nullifies relying-party.xml NameID format
In 3.2.1 configuring the NameID in relying-party.xml doesn't override what the metadata says and creates no NameID in the SAML assertion.
Read more >various nameid formats
The edge case has been "persistent", and pairwise ID is so broken that it's increasingly no longer much of a caveat to that...
Read more >SAML linking should better handle inconsistent capitalization
What Better handle the case when SAML NameID doesn't match the capitalization currently stored for a user under extern_uid.
Read more >Can okta return a nameid that is persistent, but anonymous?
The nameid typically includes some form of email (which are real names) or, well, real name. Is there some form of nameid that...
Read more >SAML - what can go wrong? Security check
In order to get the email from the NameID, you have to extract the inner text ... This is definitely an edge case...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@schriftgestalt 👑
This is not a bug in Glyphs but a misconfiguration. The
Bold Italic
instance has aBold
in the link to field. This field should be empty.