Skip to Content
0
May 24, 2020 at 06:14 AM

How to manage the security of an odata source to a schema?

187 Views Last edit May 25, 2020 at 07:58 PM 9 rev

Hello experts,

I have generated two odata services using eclipse. To do this, create a dynamic web Project and enable persistence.xml. After that I created the tables one by one in classes and then added them to the persistence.xml. I exported it in a .war file and imported it in the Java applications section in the SCP. I established a join with a binding schema that I created earlier and it generated the URL with the all functional odata.

I can only create schemas.

captura02.png

I already made this explanation on the following blog:

https://answers.sap.com/questions/13003660/how-to-create-a-third-odata-service-with-schemas-a.html

The problem now is that at the time of entering the odata service (which asks for a username and password) you can enter with any SCP user.

How can I add implement security manager in ODATA schema?

Another detail is when I enter the program HANA STUDIO, the diagrams appear without any state and when accessing, a user is auto-generated, while the one created with HANA XS (in other region) does have a state and has a user already defined.

hereas they were all created with the same eclipse WAR project (only name changed). Why do they both have so many differences? I know that one works with schema and the other with HANA XS. Is it recommended to work with schemes? Why does it not allow me to access different sections? Why are users self-generated? The security issue does not arise in the odata with HANA XS. Only certain users can access there.

HANA XS vs SCHEMA -> captura01.png






If there was any documentation about using the schema in my site, it would be helpful. I always find documentation and database examples with HANA XS and HANA MDC.

Regards.

Attachments

7m8sf.png (86.2 kB)
qdw0n.png (59.5 kB)
avcor.png (200.2 kB)
m5nfh.png (60.1 kB)
8gola.png (99.5 kB)
hgvck.png (36.5 kB)
7lkha.png (165.3 kB)
b7ozy.png (188.3 kB)
captura02.png (73.8 kB)
captura01.png (66.6 kB)