IEEE802.1x pb

[fmiu-imperosoftware]

Hi,
Cannot add more than one wired and one wireless ieee configs. After adding a wired/wireless ieee config, adding another of the same type results in
responseBody: {
error: 'Unique key violation',
message: '802.1x config: test2 already exists'
}
whatever the name of the config is.
Tried from the sample web ui (tenantId empty) and with rps api (with tenantId), the same behaviour .
The config does not exists in reality, checked with rps api. As soon as the first ieee config is deleted, another may be created, with exactly the same name that previously generated the error.

[graikhel-intel]

I deployed the toolkit using docker compose with the RPS main branch. I was able to create multiple IEEE configs for both wired and wireless through the sample-web-ui. Are there any specific steps to reproduce this? The profile name must be unique. If I try to create a profile with an existing name, then I see the unique key violation error.

[fmiu-imperosoftware]

Hi, thanks, This is good news. I forgot to say, our rps is 2.15. On this version the unique key violation error appears no matter the name, but we'll upgrade the servers at some point, probably it will work. Florin Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Ganesh Raikhelkar ***@***.***> Sent: Wednesday, October 2, 2024 9:42:06 PM To: open-amt-cloud-toolkit/rps ***@***.***> Cc: Florin Miu ***@***.***>; Author ***@***.***> Subject: Re: [open-amt-cloud-toolkit/rps] IEEE802.1x pb (Issue #1824) I deployed the toolkit using docker compose with the RPS main branch. I was able to create multiple IEEE configs for both wired and wireless through the sample-web-ui. Are there any specific steps to reproduce this? The profile name must be unique. If I try to create a profile with an existing name, then I see the unique key violation error. image.png (view on web)<https://github.com/user-attachments/assets/b6e93ae6-e9e4-4848-8e53-9524904af0cc> — Reply to this email directly, view it on GitHub<#1824 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AT3L7PFUWMQXHQT332U2IULZZQ475AVCNFSM6AAAAABPHQDIHGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBZGQ2DGMRVGE>. You are receiving this because you authored the thread.Message ID: ***@***.***> ………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………………. IMPORTANT: This email is intended for the addressee only and may contain confidential information. Any disclosure of this information is strictly prohibited and may be unlawful. If you believe that you have received this email in error, please notify us immediately by return email or telephone; do not distribute, copy or disclose the contents of this email to anyone else and please delete it from your computer system. Please do not respond to any unsolicited emails which appear to be from Impero asking for confidential or personal information. Impero has taken reasonable precautions to ensure that emails and attachments do not contain computer viruses. Impero does not accept any liability or responsibility for loss or damage sustained as a result of computer viruses and the recipient must ensure that the email and any attachments are virus free. The body of this email does not constitute a binding agreement. To read our Privacy Policy, visit www.imperosoftware.com/policies-terms.