Ok, I think there is probably one very specific issue that might be causing confusion, and this is likely something that was introduced very recently, which would be why we haven't cleaned it up yet. I'll have to check with engineering or do some tests, but here is what I think is happening:
Right now, the WAP371s you have are not running firmware that supports RESTCONF, so there is no use for the username/password combination. Up until very recently, we did not even show a username/password credential as an option for the WAP unless you were running firmware that supported RESTCONF. But we changed that not long ago, because it was too hard to keep up with the change in the WAP beta build versions. So I think you are being prompted for credentials that will always fail because the underlying API isn't there.
So I think there are actually two separate issues here:
1. The UI indicates that a username & password is required for the WAP when actually it isn't. This will not be the case at release because we will have validation in place to only request those credentials if needed.
2. The saved credential lists shows cisco/cisco as being saved for the WAP. I'm guessing you are seeing this, though I haven't tested it yet with a non-RESTCONF WAP. Anyway, if you are seeing this, then this really is a bug, because we should only store a credential that has been used successfully on this device at least once in the past.
Does all of that make sense? And if these two issues were addressed, would the workflow now make sense, or is there other areas in here that need attention?
Cheers,
Dave.
