Closed nirokato closed 6 days ago
To add the configuration in the app/src/config.js
file under the oidc
section, update the file as follows:
oidc: {
// Existing OIDC settings
peer_name: {
force: true, // Enforce using profile data for peer_name
email: true, // Use email as peer_name
name: false, // Don't use full name (family_name + given_name)
},
// other oidc settings...
},
// other config settings...
{
"email": "miroslav.pejic.85@gmail.com",
"family_name": "Pejic",
"given_name": "Miroslav",
"name": "Miroslav Pejic",
"peer_name": {
"force": true,
"email": true,
"name": false
}
}
force: true
uses profile data for peer_name
.email: true
sets the email (miroslav.pejic.85@gmail.com
) as peer_name
.name: false
ignores the full name "Miroslav Pejic"
.Thank you for your hard work on Mirotalk SFU, it is impressive.
Thank you so much for your kind words! I'm really glad you find MiroTalk SFU impressive. It’s been a great journey working on it, and your feedback means a lot. If you have any questions or ideas you'd like to explore, Feel free to join our community on Discord! You can connect with others and stay updated on all things MiroTalk SFU at https://discord.gg/rgGYfeYW3N. Looking forward to seeing you there!
Hello Miroslav,
Thank you for your hard work on Mirotalk SFU, it is impressive.
Feature request
If OIDC is enabled, there should be the option in
app/src/config.js
to set items fromreq.oidc.user
as thepeer_name
.When this option is set, peers cannot set their own
peer_name
.The following options from the
/profile
endpoint would be the most useful: "name", "preferred_username", and "email".Pros
This would allow for automatic name entry from OIDC, help prevent name collisions, and allow matching usernames to server-side recordings.