Hi,
I developed a Platform Single Sign-On extension and a corresponding extension for my IdP, which is Keycloak based. The code for both projects are here:
https://github.com/unioslo/keycloak-psso-extension
and
https://github.com/unioslo/weblogin-mac-sso-extension
I realized that, when using the Secure Enclave as the AuthenticationMethod, and according to Apple's documentation, the Extension doesn’t obtain fresh ID Tokens when they expire if the refresh token is still valid.
When using password as the Authentication Method, it fetches new ID tokens when they expire, without prompting the user for credentials, by using the refresh token.
My suggestion is that the same behavior should be implemented for Secure Enclave keys.
The thing here is that usually, on OIDC flows, the ID/Access tokens are short-lived. It would make sense for the extension to provide fresh ID tokens. It doesn’t seem to make sense for me that, when using passwords, the extension would fetch these tokens, and not when having the Secure Enclave key.
By not doing this, Apple almost forces the developer of an extension to fetch new ID tokens themselves, which doens’t make sense when it clearly provides fresh tokens when using passwords. It almost forces the developers to either implement that logic themselves, or to issue longer tokens, which is not so nice.
How so you deal with this? Do you simply use the refresh token as an authentication token, or do you do some sort of manual refresh on the extension?
General
RSS for tagExplore the intersection of business and app development. Discuss topics like device management, education, and resources for aspiring app developers.
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Created
Hi,
We developed a Platform SSO extension for our IdP, Keycloak. It would be great to get some feedback on it:
https://francisaugusto.com/2025/Platform_single_sign_on_diy/
We have been trying to figure out how to block Apple Private Relay in our enterprise so we can monitor and filter our employees traffic. We are able to block the Private Relay via this process:
We used this article from Fortinet to achieve this:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-block-iCloud-Private-Relay-from-bypassing/ta-p/228629
This also appears to block the users ability to utilize Apple iCloud Drive Backups. They would like to allow that still.
Is there a way to block iCloud Private Relay while still allowing iCloud Drive Backups to work? I am not finding a document listing the URL requirements for iCloud Drive Backups.
We currently have this solution in place:
https://community.fortinet.com/t5/FortiGate/Technical-Tip-How-to-allow-iCloud-private-relay/ta-p/383703
Basically this solution is allowing all Apple URL/IPs to go through the firewall and not be filtered. They would like to scan the traffic through. When scanning is enabled the firewall blocks the iCloud Private Relay traffic as it is blocked as being a proxy.
Any guidance is greatly appreciated.
Topic:
Business & Education
SubTopic:
General
Hey.
If i have a new idea for apple how can i reach out for you?
Topic:
Business & Education
SubTopic:
General
The profile expiration date is approaching, and no amount of inquiries will solve it.
Create a new profile
Download a new profile from Xcode
Press archive, press Distribute App, press Enterprise, and distribute
Invalid expiration date in profile of summary of review app.ipa content
I've tried everything that comes out by Googleing profiles, such as regenerating profiles, erasing caches, updating Xcode, updating macOS, deleting existing profile information, etc.
Expiration date different from the expiration date of the profile created in that menu is displayed.
The expiration date of the profile I created is December 8, 2026, and the previous certificate is January 22, 2026.
However, the profile information of the generated ipa is February 12, 2026.
So I can't distribute this app because I'm scared, and the expiration date is coming up. Users should have a period of time to update.
Get me a novice developer who's choking up.
Hi Team,
Could you please share how to change/extend the expiry date of the existing iOS Distribution (In-House) certificate?
Since the membership renewal date is in March 2026 and the iOS distribution(In-House) certificate expiry date is in Feb 2026.
We use to distribute the mobile apps using the product intunes (Company portal) and via direct download link.
Please suggest since this certificate is used by multiple mobile apps by the users which can affect lot of iPhone users?
Thank you in advance
Deepak