Subsequent patial realm exports are different from initial partial export

[zam...@gmail.com]

Hello

We are using latest Keycloak 26.0.5 and we use realm partial export feature to create a "template" for our own realms.

I have noticed, however, that, even without making any changes to realm, the initial partial export is different than exports done on other realms that were created using that initial export.

 To illustrate, try following:

All the following steps are performed from Admin Console: 

1. create a new, "blank" realm 'test1'
2. perform partial export of the realm 'test1' including groups/roles, save as 'test1-realm.json'
   1. edit 'test1-realm.json', remove all IDs and resave (so it can be used in the next step)
      
3. create another new realm 'test2' using 'test1-realm.json' as source
4. perform partial export of the realm 'test2' including groups/roles, save as 'test2-realm.json'
   1. edit 'test2-realm.json', remove all IDs and resave (so it can be used in the next step)
5. create another new realm 'test3' using 'test2-realm.json' as source
6. perform partial export of the realm 'test3' including groups/roles, save as 'test3-realm.json' 
7. compare 'test1-realm.json','test2-realm.json', and 'test3-realm.json'

I would expect these 3 exports to be identical (expect for IDs and any property value that uses realm name)...
Exports for 'test2' and 'test3' are identical but 'test1' is different from 'test2' (and 'test3' of course)
Compared to 'test1', 'test2':

• has extra property under each of "clientScopes[].protocolMappers[].config" added "userinfo.token.claim=true"
• has several extra properties in export file, including:
  • clientOfflineSessionIdleTimeout
  • clientOfflineSessionMaxLifespan
  • clientSessionIdleTimeout
  • clientSessionMaxLifespan
  • organizationsEnabled

I don't know if this is bug or by design and the question I have is - do these differences matter for templating purposes?
Or should I just use "double export" to ensure I capture all the properties required?

Thanks

Z