| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1774.1 | exit | TOOK::SHMUYLOVICH | | Thu Nov 07 1991 19:55 | 5 |
|
Thanks for pointing to this problem.
Historian and Exporter do not support "by user" and "by password".
SAm
|
| 1774.2 | A QAR has been filed against this... | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Fri Nov 08 1991 12:08 | 0 |
| 1774.3 | an answer to the related QAR | TOOK::SHMUYLOVICH | | Fri Nov 08 1991 18:13 | 16 |
| You are right. "There is no technical reason why the BY access
control qualifier cannot be passed to the historian to be used for its
polling operations."
But after recorded data are written in the Historical Repository
they are visible to every one who has an access to the directory of
the domain specified in the Record command. Is this what you want?
If I remember correctly a security issue was a reason why
Historian and Exporter do not support By User and BY Password qualifiers.
To be consistent not only Historian but also Past Time Information
Manager has to support By User and BY Password qualifiers. And this
requires a new structure of Historical Attribute Repository.
|
| 1774.4 | Yes for By Password | UTROP2::DOOLAARD_C | | Tue Nov 12 1991 20:19 | 7 |
|
I think it's a must to have By user and By Password access control for
the historian.
Take SNMP,the community name is almost never public so you can't record
anything at this moment.
Carlo.
|
| 1774.5 | | TOOK::R_SPENCE | Nets don't fail me now... | Mon Nov 18 1991 15:53 | 6 |
| I agree that in many (most?) cases the community name isn't "public"
but in most cases I have seen, the device alows more than one
community name and more than one member per comunity. Does the
device you have not permit adding "public"?
s/rob
|