Hi,

Those are actually the most up-to-date ones. Though, please note that the ‘com.prosysopc.ua.stack.transport.security.SecurityMode’ is our SDK-specific combination of com.prosysopc.ua.stack.core.MessageSecurityMode and com.prosysopc.ua.stack.transport.security.SecurityPolicy. The MessageSecurityMode is the None/Sign/signAndEncrypt and the SecurityPolicy are the policies for those (and the spec mostly talks about them separately).

The specification does specify SecurityPolicy. Related info used to be in Part 7 “Profiles”, though in later spec versions the actual data was moved unfortunately to be online only https://profiles.opcfoundation.org/ (there might be some document about these as pdf, but that is outside of this answer). If you navigate to the Security/SecurityPolicy ClientServer or use https://profiles.opcfoundation.org/profilefolder/474, you will see the

https://profiles.opcfoundation.org/profile/2058 for the Aes128 (full name is Aes128_Sha256_RsaOaep)
and
https://profiles.opcfoundation.org/profile/2060 for the Aes256 (full name is Aes256_Sha256_RsaPss)

you would see related details. Though mostly you do not need to care about that since the SDK com.prosysopc.ua.stack.transport.security.SecurityPolicy contains the relevant info (and it is mostly for SDKs e.g. bit lengths, algorithm names etc.).

Generally speaking the SecurityModes should be initialized like shown in the com.prosysopc.ua.samples.server.SampleConsoleServer.initialize(int, int, String), i.e. you will chose set of policies and messagesecurity modes and then do

server.getSecurityModes().addAll(SecurityMode.combinations(supportedMessageSecurityModes, supportedSecurityPolicies));

and the SDK will create valid combinations of them.

P.S.
Also as per the samples do note the comment
/*
* Per the 1.05 specification, only these policies should be supported and the older ones should
* be considered as deprecated. However, in practice this list only contains very new security
* policies, which most of the client applications as of today that are used might not be unable
* to (yet) use. Thus, you should build a way to select these in your application configuration.
*
* Note that the 1.05 list has the same contents as the 1.04 list.
*/
supportedSecurityPolicies.addAll(SecurityPolicy.ALL_SECURE_104);
supportedSecurityPolicies.addAll(SecurityPolicy.ALL_SECURE_105);