CORRECTION OF MY LAST ANSWERAfter I figured out a lot more about OAuth2 and I think I am understanding now how the Client Credential Flow and the Resource Owner Password Flow are working. As I mentioned in my last answer there are two different ways to authenticate:"native"/"public": Without Client-Secret "web"/"confidential": With Client-SecretThe reason why these two ways exists is explained here: https://auth0.com/docs/get-started/authentication-and-authorization-flow/authorization-code-flow-with-proof-key-for-code-exchange-pkceAnd to correct my last answer:It doesn`t matter if you use the public login or the confidential login. Both are working for the WebAPI. SOLUTIONThe point where I was getting confused by the documentation was at the following line:Give an Identifier. For documentation purposes giving the application server URL as the identifier is a good idea. If the identifier of this WebAPI is freely configurable, the IFS middleware server cannot know it and thereby cannot
UPDATEAs far as we understand it there are two different ways to authenticate for IFS Applications 10:Native: This is used for native applications like the IEE. Since the client runs on the local user machine, in theory a client secret could be acquired by anybody. Therefore only the client id (native) is needed. Web: This is used for WebAPIs. The client secret is hidden by the backend server and cannot be acquired by anybody. Therefore the client id (web) and the client secret (web) is needed.The same two ways of authentication are available for ADFS servers. This is controlled by the "resource" parameter.Native: api://PTY10 Web: ifs-pty01.me-group.local:51080We now have a test case where we request a native access token from the internal IFS OAuth server.As expected this access token does not work for the WebAPI. If we do the same test case with a web access token from the internal IFS OAuth server we are able to use the WebAPI.So far everything as expected. For the ADFS server
@Vidar: Thank you so much for helping me!
Also no success with:[...]/main/ifsapplications/web/page/CCtiLandingPage/CCtiLandingPage?initcontext=NumberRaw:’123’
Thank you for your reply Sameera.I think the problem that FRSMDE is facing is similar to the problem described in this question:There is no problem for your particular case with ‘Purchase Orders’ because you can use the ‘Purchase Order Lines’ function to search for orders which, for example, has released or confirmed lines.But if you consider FRSMDE’s example with suppliers and addresses, we have the problem that there is no function with which we can, for example, search for suppliers which have a certain zip code. In the enterprise explorer we solved this problem by making a sub-select in the advanced search. Unfortunately this is no longer possible in Aurena.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
